Consent receipt management systems and related methods

ABSTRACT

In particular embodiments, a consent receipt management system is configured to track and analyze one or more attributes of a user interface via which data subjects are requested to provide consent (e.g., consent to process, collect, and/or store personal data) in order to determine which of the one or more attributes are more likely to result in a successful receipt of consent from a data subject. For example, the system may be configured to analyze one or more instances in which one or more data subjects provided or did not provide consent in order to identify particular attributes and/or factors that may increase a likelihood of a data subject providing consent.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/594,670, filed Oct. 7, 2019, which is a continuation-in-part of U.S.patent application Ser. No. 16/278,123, filed Feb. 17, 2019, now U.S.Pat. No. 10,437,412, issued Oct. 8, 2019, which claims priority fromU.S. Provisional Patent Application Ser. No. 62/631,684, filed Feb. 17,2018 and U.S. Provisional Patent Application Ser. No. 62/631,703, filedFeb. 17, 2018, and is also a continuation-in-part of U.S. patentapplication Ser. No. 16/159,634, filed Oct. 13, 2018, now U.S. Pat. No.10,282,692, issued May 7, 2019, which claims priority from U.S.Provisional Patent Application Ser. No. 62/572,096, filed Oct. 13, 2017and U.S. Provisional Patent Application Ser. No. 62/728,435, filed Sep.7, 2018, and is also a continuation-in-part of U.S. patent applicationSer. No. 16/055,083, filed Aug. 4, 2018, now U.S. Pat. No. 10,289,870,issued May 14, 2019, which claims priority from U.S. Provisional PatentApplication Ser. No. 62/547,530, filed Aug. 18, 2017, and is also acontinuation-in-part of U.S. Patent application Ser. No. 15/996,208,filed Jun. 1, 2018, now U.S. Pat. No. 10,181,051, issued Jan. 15, 2019,which claims priority from U.S. Provisional Patent Application Ser. No.62/537,839, filed Jul. 27, 2017, and is also a continuation-in-part ofU.S. patent application Ser. No. 15/853,674, filed Dec. 22, 2017, nowU.S. Pat. No. 10,019,597, issued Jul. 10, 2018, which claims priorityfrom U.S. Provisional Patent Application Ser. No. 62/541,613, filed Aug.4, 2017, and is also a continuation-in-part of U.S. patent applicationSer. No. 15/619,455, filed Jun. 10, 2017, now U.S. Pat. No. 9,851,966,issued Dec. 26, 2017, which is a continuation-in-part of U.S. patentapplication Ser. No. 15/254,901, filed Sep. 1, 2016, now U.S. Pat. No.9,729,583, issued Aug. 8, 2017, which claims priority from: (1) U.S.Provisional Patent Application Ser. No. 62/360,123, filed Jul. 8, 2016;(2) U.S. Provisional Patent Application Ser. No. 62/353,802, filed Jun.23, 2016; and (3) U.S. Provisional Patent Application Ser. No.62/348,695, filed Jun. 10, 2016. The disclosures of all of the abovepatents and patent applications are hereby incorporated herein byreference in their entirety.

BACKGROUND

Over the past years, privacy and security policies, and relatedoperations have become increasingly important. Breaches in security,leading to the unauthorized access of personal data (which may includesensitive personal data) have become more frequent among companies andother organizations of all sizes. Such personal data may include, but isnot limited to, personally identifiable information (PII), which may beinformation that directly (or indirectly) identifies an individual orentity. Examples of PII include names, addresses, dates of birth, socialsecurity numbers, and biometric identifiers such as a person'sfingerprints or picture. Other personal data may include, for example,customers' Internet browsing habits, purchase history, or even theirpreferences (e.g., likes and dislikes, as provided or obtained throughsocial media).

Many organizations that obtain, use, and transfer personal data,including sensitive personal data, have begun to address these privacyand security issues. To manage personal data, many companies haveattempted to implement operational policies and processes that complywith legal and industry requirements. However, there is an increasingneed for improved systems and methods to manage personal data in amanner that complies with such policies.

SUMMARY

A computer-implemented data processing method for optimizing consent fora transaction, in various embodiments, comprises: (1) providing, by oneor more processors, to a plurality of data subjects, a user interfacefor initiating a transaction between an entity and each respective datasubject of the plurality of data subjects; (2) receiving, by one or moreprocessors, one or more requests to initiate the transaction from atleast a portion of the plurality of data subjects; (4) analyzing, by oneor more processors, the one or more requests to identify one or moreattributes of the user interface; (5) analyzing, by one or moreprocessors, the one or more attributes of the user interface todetermine at least one attribute of the one or more attributes thatincrease a likelihood that a particular data subject will submit arequest to initiate the transaction; (6) analyzing the plurality of datasubjects to categorize the plurality of data subjects based on one ormore data subject attributes; (7) storing an indication of the at leastone attribute in computer memory; and (8) generating a custom interfacefor initiating the transaction based at least in part on the one or moredata subject attributes and the at least one attribute.

A computer-implemented data processing method for managing a consentreceipt under a transaction, in various embodiments, comprises: (1)providing, by one or more processors, a user interface for initiating atransaction between an entity and a data subject; (2) receiving, by oneor more processors, a request to initiate a transaction between theentity and the data subject; (3) in response to the request, generating,by a third party consent receipt management system, a unique consentreceipt key; (4) receiving, by one or more processors, from the datasubject, a unique subject identifier; (5) electronically storing, by oneor more processors, the unique subject identifier, the unique consentreceipt key, and a unique transaction identifier associated with thetransaction in computer memory; (6) electronically associating, by oneor more processors, the unique subject identifier, the unique consentreceipt key, and the unique transaction identifier; (7) identifying oneor more triggering events related to the transaction; and (8)automatically causing the unique consent receipt key to expire inresponse to identifying the one or more triggering events.

A computer-implemented data processing method for managing a consentreceipt under a transaction, in various embodiments, comprises: (1)providing a user interface for initiating a transaction between anentity and a data subject; (2) receiving, from a computing deviceassociated with the data subject via the user interface, a request toinitiate a transaction between the entity and the data subject; (3) inresponse to receiving the request: (A) generating, by a consent receiptmanagement system, a unique consent receipt key; and (B) initiating avirtual browsing session on a consent receipt capture server; (C)accessing a webpage hosting the user interface using a virtual browserduring the virtual browsing session; (D) scanning the webpage toidentify the user interface; and (E) capturing the user interface in anunfilled state; (4) electronically storing a unique subject identifierassociated with the data subject, the unique consent receipt key, aunique transaction identifier associated with the transaction, and thecapture of the user interface in computer memory; (5) electronicallyassociating the unique subject identifier, the unique consent receiptkey, the unique transaction identifier, and the capture of the userinterface; (6) in response to receiving the request, optionallytransmitting a consent receipt to the data subject, the consent receiptcomprising at least the unique subject identifier and the unique consentreceipt key; (7) identifying one or more triggering events related tothe transaction; and (8) automatically causing the unique consentreceipt key to expire in response to identifying the one or moretriggering events.

A computer-implemented data processing method for managing a consentreceipt under a transaction, in some embodiments, comprises: (1)providing a user interface for initiating a transaction between anentity and a data subject; (2) receiving a request to initiate atransaction between the entity and the data subject; (3) in response tothe request: (A) initiating the transaction; and (B) generating, usingone or more consent receipt generation means, a unique consent receiptkey; (4) identifying a privacy policy associated with the transaction;(5) receiving, from the data subject, a unique subject identifierelectronically storing the unique subject identifier, the unique consentreceipt key, the privacy policy, and a unique transaction identifierassociated with the transaction in computer memory using one or moreelectronic storage means; (6) electronically associating the uniquesubject identifier, the unique consent receipt key, the privacy policy,and the unique transaction identifier; identifying one or moretriggering events related to the transaction; and (7) automaticallycausing the unique consent receipt key to expire in response toidentifying the one or more triggering events.

A consent receipt management system, according to any embodimentdescribed herein, may comprise: (1) one or more processors; and (2)computer memory. In any embodiment described herein, the consent receiptmanagement system may be configured for: (1) receiving a request toinitiate a transaction between an entity and a data subject, thetransaction involving collection or processing of personal dataassociated with the data subject by the entity as part of a processingactivity undertaken by the entity that the data subject is consenting toas part of the transaction; (2) in response to receiving the request:(A) identifying a transaction identifier associated with thetransaction; (B) generating, a unique consent receipt key for thetransaction; and (C) determining a unique subject identifier for thedata subject; (3) electronically storing the unique subject identifier,the unique consent receipt key, and the transaction identifier incomputer memory; (4) electronically associating the unique subjectidentifier, the unique consent receipt key, and the transactionidentifier; (5) generating a consent record for the transaction, theconsent receipt comprising at least the unique subject identifier andthe unique consent receipt key; and (6) electronically transmitting theconsent record to the data subject.

A computer-implemented data processing method for managing a consentreceipt under a transaction, in any embodiment described herein, maycomprise: (1) providing a user interface for initiating a transactionbetween an entity and a data subject; (2) receiving a request toinitiate a transaction between the entity and the data subject; (3) inresponse to the request, generating, by a third party consent receiptmanagement system, a unique consent receipt key; (4) receiving, from thedata subject, a unique subject identifier; (5) electronically storingthe unique subject identifier, the unique consent receipt key, and aunique transaction identifier associated with the transaction incomputer memory; (6) electronically associating the unique subjectidentifier, the unique consent receipt key, and the unique transactionidentifier; and (7) in response to receiving the request, transmitting aconsent receipt to the data subject, the consent receipt comprising atleast the unique subject identifier and the unique consent receipt key.

A computer-implemented data processing method for identifying one ormore pieces of personal data associated with a data subject within adata system in order to fulfill a data subject access request, in anyembodiment described herein, comprises: (1) receiving, by one or moreprocessors, from a data subject, a data subject access request; (2)processing the data subject access request by identifying the one ormore pieces of personal data associated with the data subject; and (3)in response to identifying the one or more pieces of personal data,taking one or more actions such as, for example: (1) deleting the one ormore pieces of personal data from the data system; (2) modifying atleast one of the one or more pieces of personal data and storing themodified at least one of the one or more pieces of personal data in thedata system; and (3) generating a report comprising the one or morepieces of personal data and providing the report to the data subject. Invarious embodiments, identifying the one or more pieces of personal dataassociated with the data subject comprises scanning one or more datainventories stored within the data system for the one or more pieces ofpersonal data;

A data processing data inventory generation system, according to variousembodiments, comprises: (1) one or more processors; (2) computer memory;and (3) a computer-readable medium storing computer-executableinstructions. In various embodiments, the computer-executableinstructions, when executed by the one or more processors, cause the oneor more processors to perform operations comprising: (1) identifying aprimary data asset that collects or stores personal data of one or moredata subjects; and (2) generating a data inventory for the primary dataasset, the data inventory storing one or more primary data assetinventory attributes. In particular embodiments, the one or more primarydata asset inventory attributes comprise: (1) a type of personal datacollected or stored by the primary data asset; and (2) primary transferdata associated with the personal data and the primary data asset. Inparticular embodiments, the computer-executable instructions, whenexecuted by the one or more processors, further cause the one or moreprocessors to perform operations comprising: (1) identifying a transferdata asset based at least in part on the primary transfer data; (2)modifying the data inventory to include the transfer data asset, thetransfer data asset storing one or more transfer data asset inventoryattributes comprising the primary transfer data; (3) digitally storingthe data inventory in the computer memory; and (4) electronicallylinking the primary data asset to the transfer data asset in the datainventory.

A computer-implemented data processing method of generating a datainventory for a plurality of inter-related data assets utilized in theprocessing of one or more pieces of personal data, according to variousembodiments, comprises: (1) identifying, by one or more processors, fromthe plurality of inter-related data assets, a storage asset, the storageasset storing the one or more pieces of personal data collected from oneor more data subjects; (2) identifying, by one or more processors, fromthe plurality of inter-related data assets, a collection asset thattransfers the one or more pieces of personal data to the storage asset;(3) identifying, by one or more processors, from the plurality ofinter-related data assets, a transfer asset to which the storage assettransfers the one or more pieces personal data; (4) digitally storing,by one or more processors, in computer memory, one or more storage assetinventory attributes comprising a type of personal data stored by thestorage asset; (5) digitally storing, by one or more processors, incomputer memory, one or more collection asset inventory attributescomprising the one or more pieces of personal data that the collectionasset transfers to the storage asset; (6) digitally storing, by one ormore processors, in computer memory, one or more transfer assetinventory attributes comprising the one or more pieces of personal datathat the storage asset transfers to the transfer asset; and (7)generating the data inventory.

In particular embodiments, generating the data inventory comprises: (1)associating the storage asset with the one or more storage assetinventory attributes in computer memory; (2) associating the collectionasset with the one or more collection asset inventory attributes incomputer memory; (3) associating the transfer asset with the one or moretransfer asset inventory attributes in computer memory; (4)electronically linking the collection asset to the storage asset incomputer memory; (5) electronically linking the storage asset to thetransfer asset; and (6) electronically mapping the one or more pieces ofpersonal data to the collection asset, the storage asset, and thetransfer asset.

A computer-implemented data processing method for generating a datamodel of personal data processing activities, according to particularembodiments, comprises: (1) generating a data model for one or more dataassets used in the collection or storage of personal data; (2) digitallystoring the data model in computer memory; (3) identifying a first dataasset of the one or more data assets; (4) modifying the data model toinclude the first data asset; (5) generating a data inventory for thefirst data asset in the data model; (6) associating the data inventorywith the first data asset in computer memory; and (7) mapping the firstdata asset to at least one of the one or more data assets in the datamodel. In various embodiments, the data inventory comprises one or moreinventory attributes such as, for example: (1) one or more processingactivities associated with the first data asset; (2) transfer dataassociated with the first data asset; and (3) one or more pieces ofpersonal data associated with the first asset.

Various embodiments are also described in the following listing ofconcepts:

1. A computer-implemented data processing method for optimizing consentfor a transaction, in particular embodiments, comprises:

providing, by one or more processors, to a first plurality of datasubjects, a first user interface having a first set of user interfaceattributes to each respective data subject of the first plurality ofdata subjects, the first user interface being a first user interface forinitiating a transaction between an entity and each respective datasubject of the first plurality of data subjects;

providing, by one or more processors, to a second plurality of datasubjects, a second user interface having a second set of user interfaceattributes to each respective data subject of the second plurality ofdata subjects, the second user interface being a second user interfacefor initiating a transaction between the entity and each respective datasubject of the second plurality of data subjects;

receiving, by one or more processors, one or more first requests toinitiate the transaction from at least a first portion of the firstplurality of data subjects;

receiving, by one or more processors, one or more second requests toinitiate the transaction from at least a second portion of the secondplurality of data subjects;

analyzing, by one or more processors, the one or more first requests andthe one or more second requests to identify one or more commonattributes among the first set of user interface attributes and thesecond set of user interface attributes;

analyzing, by one or more processors, the one or more common attributesof the first user interface and the second user interface to determine,based on the one or more first requests and the one or more secondrequests, at least one attribute that increases a likelihood that aparticular data subject will submit a request to initiate thetransaction;

storing an indication of the one or more common attributes in computermemory; and

generating a custom consent interface for initiating the transactionbased at least in part on the and the at least one attribute.

2. The computer-implemented data processing method of Concept 1, inparticular embodiments, further comprises:

analyzing the first portion of the first plurality of data subjects tocategorize the first portion of the first plurality of data subjectsbased on one or more first data subject attributes;

analyzing the second portion of the second plurality of data subjects tocategorize the second portion of the second plurality of data subjectsbased on one or more second data subject attributes; and

comparing the one or more first data subject attributes and the one ormore second data subject attributes to identify one or more shared datasubject attributes;

generating the custom consent interface for initiating the transactionbased at least further in part on the one or more shared data subjectattributes.

3. The computer-implemented data processing method of Concept 2,wherein, in particular embodiments, the one or more shared data subjectattributes are selected from the group consisting of:

age;

gender; and

occupation.

4. The computer-implemented data processing method of Concept 1,wherein, in particular embodiments, generating the custom interfacecomprises determining a layout of the custom interface based at least inpart on the at least one attribute.

5. The computer-implemented data processing method of Concept 1,wherein, in particular embodiments, the one or more common attributescomprise:

a time of day at which the first plurality of data subjects was providedthe first user interface; and

a time of day at which the second plurality of data subjects wasprovided the second user interface.

6. The computer-implemented data processing method of Concept 5,wherein, in particular embodiments, the transaction comprisesprocessing, by the entity, one or more pieces of personal dataassociated with the first plurality of data subjects and the secondplurality of data subjects.

7. The computer-implemented data processing method of Concept 1,wherein, in particular embodiments, the first user interface is thesecond user interface.

8. The computer-implemented data processing method of Concept 1, inparticular embodiments, further comprises:

tracking a number of the first plurality of data subjects that viewedthe first user interface;

determining, based at least in part on the first portion of the firstplurality of data subjects, an overall opt-in percentage for the firstuser interface; and

displaying the number of the first plurality of data subjects thatviewed the first user interface and the overall opt-in percentage to afirst user via a consent conversion interface.

9. The computer-implemented data processing method of Concept 8,wherein, in particular embodiments:

the transaction comprises one or more transaction options; and

the method further comprises tracking a selection of each of the one ormore transaction options and displaying the selection of each of the oneor more transaction options as part of the consent conversion interface.

10. A computer-implemented data processing method for optimizing consentfor a transaction, in various embodiments, comprises:

providing, by one or more processors, to a plurality of data subjects, auser interface for initiating a transaction between an entity and eachrespective data subject of the plurality of data subjects;

at least partially in response to providing the user interface to theplurality of data subjects, receiving, by one or more processors, one ormore requests to initiate the transaction from at least a first portionof the plurality of data subjects;

analyzing, by one or more processors, the one or more requests toidentify one or more first factors associated with at least a firstportion of the one or more requests;

analyzing, by one or more processors, the one or more first factors ofthe user interface to determine at least one factor of the one or morefirst factors that increase a likelihood that a particular data subjectwill submit a request to initiate the transaction; and

storing an indication of the at least one factor in computer memory.

11. The computer-implemented data processing method of Concept 10,wherein, in particular embodiments, the one or more first factorscomprise a time of day at which each of the plurality of data subjectsviewed the user interface.

12. The computer-implemented data processing method of Concept 10,wherein, in various embodiments:

the user interface comprises an electronic message; and

the one or more first factors comprise a length of the electronicmessage.

13. The computer-implemented data processing method of Concept 12,wherein, in particular embodiments, the one or more first factorscomprise an opt-down option within the electronic message.

14. The computer-implemented data processing method of Concept 10, inparticular embodiments, further comprises: generating a new userinterface for initiating the transaction based at least in part on theat least one factor.

15. The computer-implemented data processing method of Concept 14,wherein generating the new user interface may comprise generating thenew user interface to not include one or more of the one or moreattributes.

16. The computer-implemented data processing method of Concept 15,wherein the method may further comprise providing the new user interfaceto the plurality of data subjects that do not include the at least aportion of the plurality of data subjects.

17. A consent receipt analysis, processing, and custom interfacegeneration system comprising:

one or more processors;

computer memory; and

a non-transitory computer-readable medium storing computer-executableinstructions that, when executed by the one or more processors, causethe one or more processors to perform operations comprising:

-   -   providing, by one or more processors, to a first plurality of        data subjects, a first user interface having a first set of user        interface factors to each respective data subject of the first        plurality of data subjects, the first user interface being a        first user interface for initiating a first transaction between        an entity and each respective data subject of the first        plurality of data subjects;    -   providing, by one or more processors, to a second plurality of        data subjects, a second user interface having a second set of        user interface factors to each respective data subject of the        second plurality of data subjects, the second user interface        being a second user interface for initiating a second        transaction between the entity and each respective data subject        of the second plurality of data subjects;    -   receiving, by one or more processors, one or more first requests        to initiate the first transaction from at least a first portion        of the first plurality of data subjects;    -   receiving, by one or more processors, one or more second        requests to initiate the second transaction from at least a        second portion of the second plurality of data subjects;    -   analyzing, by one or more processors, the one or more first        requests and the one or more second requests to identify one or        more common factors among the first set of user interface        factors and the second set of user interface factors;    -   analyzing, by one or more processors, the one or more common        factors of the first user interface and the second user        interface to determine, based on the one or more first requests        and the one or more second requests; at least one factor that        increases a likelihood that a particular data subject will        submit a request to initiate the first transaction or the second        transaction;    -   storing an indication of the at least one factor in computer        memory; and    -   generating a custom consent interface for initiating a third        transaction based at least in part on the at least one factor.

18. The consent receipt analysis, processing, and custom interfacegeneration system of Concept 17, wherein the one or more common factorsmay include, for example:

a type of the first transaction;

a type of the second transaction;

a number of first opt-down options available via the first userinterface;

a number of second opt-down options available via the first userinterface;

a time of day at which the first user interface was provided to thefirst plurality of data subjects;

a time of day at which the second user interface was provided to thesecond plurality of data subjects;

an age of the first plurality of data subjects;

an age of the second plurality of data subjects;

a gender of the first plurality of data subjects; and

a gender of the second plurality of data subjects.

19. The consent receipt analysis, processing, and custom interfacegeneration system of Concept 18, wherein the one or more common factorscomprise a type of the first transaction and a type of the secondtransaction.

20. The consent receipt analysis, processing, and custom interfacegeneration system of Concept 17, wherein the non-transitorycomputer-readable medium further stores computer-executable instructionsthat, when executed by the one or more processors, cause the one or moreprocessors to perform operations comprising providing the custom consentinterface to a second portion of the first plurality of data subjectsthat does not include the first portion of the first plurality of datasubjects.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a data subject access request fulfillment systemare described below. In the course of this description, reference willbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 depicts a data model generation and population system accordingto particular embodiments.

FIG. 2 is a schematic diagram of a computer (such as the data modelgeneration server 110, or data model population server 120) that issuitable for use in various embodiments of the data model generation andpopulation system shown in FIG. 1.

FIG. 3 is a flowchart showing an example of steps performed by a DataModel Generation Module according to particular embodiments.

FIGS. 4-10 depict various exemplary visual representations of datamodels according to particular embodiments.

FIG. 11 is a flowchart showing an example of steps performed by a DataModel Population Module.

FIG. 12 is a flowchart showing an example of steps performed by a DataPopulation Questionnaire Generation Module.

FIG. 13 is a process flow for populating a data inventory according to aparticular embodiment using one or more data mapping techniques.

FIGS. 14-25 depict exemplary screen displays and graphical userinterfaces (GUIs) according to various embodiments of the system, whichmay display information associated with the system or enable access to,or interaction with, the system by one or more users (e.g., to configurea questionnaire for populating one or more inventory attributes for oneor more data models, complete one or more assessments, etc.).

FIG. 26 is a flowchart showing an example of steps performed by anIntelligent Identity Scanning Module.

FIG. 27 is schematic diagram of network architecture for an intelligentidentity scanning system 2700 according to a particular embodiment.

FIG. 28 is a schematic diagram of an asset access methodology utilizedby an intelligent identity scanning system 2700 in various embodimentsof the system.

FIG. 29 is a flowchart showing an example of a processes performed by aData Subject Access Request Fulfillment Module 2900 according to variousembodiments.

FIGS. 30-31 depict exemplary screen displays and graphical userinterfaces (GUIs) according to various embodiments of the system, whichmay display information associated with the system or enable access to,or interaction with, the system by one or more users (e.g., for thepurpose of submitting a data subject access request or other suitablerequest).

FIGS. 32-35 depict exemplary screen displays and graphical userinterfaces (GUIs) according to various embodiments of the system, whichmay display information associated with the system or enable access to,or interaction with, the system by one or more users (e.g., for thepurpose of flagging one or more risks associated with one or moreparticular questionnaire questions).

FIG. 36 depicts a schematic diagram of a centralized data repositorysystem according to particular embodiments of the present system.

FIG. 37 is data repository module according to various embodiments,which may, for example, be executed by the centralized data repositorysystem of FIG. 36.

FIG. 38 depicts a schematic diagram of a consent receipt managementsystem according to particular embodiments.

FIGS. 39-54 are computer screen shots that demonstrate the operation ofvarious embodiments.

FIG. 55 depicts an exemplary consent receipt management system accordingto particular embodiments.

FIG. 56 is a flow chart showing an example of a process performed by aConsent Receipt Management Module 5600 according to particularembodiments.

FIG. 57 is a flow chart showing an example of a process performed by aConsent Expiration and Re-Triggering Module 5700 according to particularembodiments.

FIG. 58 depicts an exemplary screen display and graphical user interface(GUI) according to various embodiments of the system, which may displayinformation associated with the system or enable access to, orinteraction with, the system by one or more users (e.g., for the purposeof analyzing one or more consent conversion analytics).

FIG. 59 is a flow chart showing an example of a process performed by aConsent Validity Scoring Module 5900 according to particularembodiments.

DETAILED DESCRIPTION

Various embodiments now will be described more fully hereinafter withreference to the accompanying drawings. It should be understood that theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Rather, theseembodiments are provided so that this disclosure will be thorough andcomplete, and will fully convey the scope of the invention to thoseskilled in the art. Like numbers refer to like elements throughout.

Overview

A data model generation and population system, according to particularembodiments, is configured to generate a data model (e.g., one or moredata models) that maps one or more relationships between and/or among aplurality of data assets utilized by a corporation or other entity(e.g., individual, organization, etc.) in the context, for example, ofone or more business processes. In particular embodiments, each of theplurality of data assets (e.g., data systems) may include, for example,any entity that collects, processes, contains, and/or transfers data(e.g., such as a software application, “internet of things” computerizeddevice, database, web site, data-center, server, etc.). For example, afirst data asset may include any software or device (e.g., server orservers) utilized by a particular entity for such data collection,processing, transfer, storage, etc.

As shown in FIGS. 4 and 5, in various embodiments, the data model maystore the following information: (1) the organization that owns and/oruses a particular data asset (a primary data asset, which is shown inthe center of the data model in FIG. 4); (2) one or more departmentswithin the organization that are responsible for the data asset; (3) oneor more software applications that collect data (e.g., personal data)for storage in and/or use by the data asset (e.g., or one or more othersuitable collection assets from which the personal data that iscollected, processed, stored, etc. by the primary data asset issourced); (4) one or more particular data subjects (or categories ofdata subjects) that information is collected from for use by the dataasset; (5) one or more particular types of data that are collected byeach of the particular applications for storage in and/or use by thedata asset; (6) one or more individuals (e.g., particular individuals ortypes of individuals) that are permitted to access and/or use the datastored in, or used by, the data asset; (7) which particular types ofdata each of those individuals are allowed to access and use; and (8)one or more data assets (destination assets) that the data istransferred to for other use, and which particular data is transferredto each of those data assets. As shown in FIGS. 6 and 7, the system mayalso optionally store information regarding, for example, which businessprocesses and processing activities utilize the data asset.

In particular embodiments, the data model stores this information foreach of a plurality of different data assets and may include linksbetween, for example, a portion of the model that provides informationfor a first particular data asset and a second portion of the model thatprovides information for a second particular data asset.

In various embodiments, the data model generation and population systemmay be implemented in the context of any suitable privacy managementsystem that is configured to ensure compliance with one or more legal orindustry standards related to the collection and/or storage of privateinformation. In various embodiments, a particular organization,sub-group, or other entity may initiate a privacy campaign or otheractivity (e.g., processing activity) as part of its business activities.In such embodiments, the privacy campaign may include any undertaking bya particular organization (e.g., such as a project or other activity)that includes the collection, entry, and/or storage (e.g., in memory) ofany personal data associated with one or more individuals. In particularembodiments, a privacy campaign may include any project undertaken by anorganization that includes the use of personal data, or any otheractivity that could have an impact on the privacy of one or moreindividuals.

In any embodiment described herein, personal data may include, forexample: (1) the name of a particular data subject (which may be aparticular individual); (2) the data subject's address; (3) the datasubject's telephone number; (4) the data subject's e-mail address; (5)the data subject's social security number; (6) information associatedwith one or more of the data subject's credit accounts (e.g., creditcard numbers); (7) banking information for the data subject; (8)location data for the data subject (e.g., their present or pastlocation); (9) internet search history for the data subject; and/or (10)any other suitable personal information, such as other personalinformation discussed herein. In particular embodiments, such personaldata may include one or more cookies (e.g., where the individual isdirectly identifiable or may be identifiable based at least in part oninformation stored in the one or more cookies).

In particular embodiments, when generating a data model, the system may,for example: (1) identify one or more data assets associated with aparticular organization; (2) generate a data inventory for each of theone or more data assets, where the data inventory comprises informationsuch as: (a) one or more processing activities associated with each ofthe one or more data assets, (b) transfer data associated with each ofthe one or more data assets (data regarding which data is transferredto/from each of the data assets, and which data assets, or individuals,the data is received from and/or transferred to, (c) personal dataassociated with each of the one or more data assets (e.g., particulartypes of data collected, stored, processed, etc. by the one or more dataassets), and/or (d) any other suitable information; and (3) populate thedata model using one or more suitable techniques.

In particular embodiments, the one or more techniques for populating thedata model may include, for example: (1) obtaining information for thedata model by using one or more questionnaires associated with aparticular privacy campaign, processing activity, etc.; (2) using one ormore intelligent identity scanning techniques discussed herein toidentify personal data stored by the system and map such data to asuitable data model, data asset within a data model, etc.; (3) obtaininginformation for the data model from a third-party application (or otherapplication) using one or more application programming interfaces (API);and/or (4) using any other suitable technique.

In particular embodiments, the system is configured to generate andpopulate a data model substantially on the fly (e.g., as the systemreceives new data associated with particular processing activities). Instill other embodiments, the system is configured to generate andpopulate a data model based at least in part on existing informationstored by the system (e.g., in one or more data assets), for example,using one or more suitable scanning techniques described herein.

As may be understood in light of this disclosure, a particularorganization may undertake a plurality of different privacy campaigns,processing activities, etc. that involve the collection and storage ofpersonal data. In some embodiments, each of the plurality of differentprocessing activities may collect redundant data (e.g., may collect thesame personal data for a particular individual more than once), and maystore data and/or redundant data in one or more particular locations(e.g., on one or more different servers, in one or more differentdatabases, etc.). In this way, a particular organization may storepersonal data in a plurality of different locations which may includeone or more known and/or unknown locations. By generating and populatinga data model of one or more data assets that are involved in thecollection, storage and processing of such personal data, the system maybe configured to create a data model that facilitates a straightforwardretrieval of information stored by the organization as desired. Forexample, in various embodiments, the system may be configured to use adata model in substantially automatically responding to one or more dataaccess requests by an individual (e.g., or other organization). Variousembodiments of a system for generating and populating a data model aredescribed more fully below.

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireone or more of: (1) consent from a data subject from whom the personaldata is collected and/or processed; and/or (2) a lawful basis for thecollection and/or processing of the personal data. In variousembodiments, the entity may be required to, for example: (1) demonstratethat a data subject has freely given specific, informed, and unambiguousindication of the data subject's agreement to the processing of his orher personal data (e.g., in the form of a statement or clear affirmativeaction); (2) demonstrate that the entity received consent from a datasubject in a manner clearly distinguishable from other matters (e.g., inan intelligible and easily accessible form, using clear and plainlanguage, etc.); (3) enable a data subject to withdraw consent as easilyas the data subject can give consent; (4) separate a data subject'sconsent from performance under any contract unless such processing isnecessary for performance under the contract; etc.

In various embodiments, a consent receipt management system may beimplemented in the context of any suitable privacy management systemthat is configured to ensure compliance with one or more legal orindustry standards related to the collection and/or storage of privateinformation (e.g., such as personal data). Various privacy and securitypolicies (e.g., such as the European Union's General Data ProtectionRegulation, and other such policies) may provide data subjects (e.g.,individuals, organizations, or other entities) with certain rightsrelated to the data subject's personal data that is collected, stored,or otherwise processed by an organization. These rights may include, forexample: (1) a right to erasure of the data subject's personal data(e.g., in cases where no legal basis applies to the processing and/orcollection of the personal data; (2) a right to withdraw consent to theprocessing and/or collection of their personal data; (3) a right toreceive the personal data concerning the data subject, which he or shehas provided to an entity (e.g., organization), in a structured,commonly used and machine-readable format; and/or (4) any other rightwhich may be afforded to the data subject under any applicable legaland/or industry policy.

In particular embodiments, the consent receipt management system isconfigured to: (1) enable an entity to demonstrate that valid consenthas been obtained for each particular data subject for whom the entitycollects and/or processes personal data; and (2) enable one or more datasubjects to exercise one or more rights described herein.

The system may, for example, be configured to track data on behalf of anentity that collects and/or processes personal data related to: (1) whoconsented to the processing or collection of personal data (e.g., thedata subject themselves or a person legally entitled to consent on theirbehalf such as a parent, guardian, etc.); (2) when the consent was given(e.g., a date and time); (3) what information was provided to theconsenter at the time of consent (e.g., a privacy policy, what personaldata would be collected following the provision of the consent, for whatpurpose that personal data would be collected, etc.); (4) how consentwas received (e.g., one or more copies of a data capture form, web form,etc. via which consent was provided by the consenter); (5) when consentwas withdrawn (e.g., a date and time of consent withdrawal if theconsenter withdraws consent); and/or (6) any other suitable data relatedto receipt or withdrawal of consent. In particular embodiments, thesystem is configured to store metadata in association with processedpersonal data that indicates one or more pieces of consent data thatauthorized the processing of the personal data.

In further embodiments, the system may be configured to provide datasubjects with a centralized interface that is configured to: (1) provideinformation regarding each of one or more valid consents that the datasubject has provided to one or more entities related to the collectionand/or processing of their personal data; (2) provide one or moreperiodic reminders regarding the data subject's right to withdrawpreviously given consent (e.g., every 6 months in the case ofcommunications data and metadata, etc.); (3) provide a withdrawalmechanism for the withdrawal of one or more previously provided validconsents (e.g., in a format that is substantially similar to a format inwhich the valid consent was given by the data subject); (4) refreshconsent when appropriate (e.g., the system may be configured to elicitupdated consent in cases where particular previously validly consentedto processing is used for a new purpose, a particular amount of time haselapsed since consent was given, etc.).

In particular embodiments, the system is configured to manage one ormore consent receipts between a data subject and an entity. In variousembodiments, a consent receipt may include a record (e.g., a data recordstored in memory and associated with the data subject) of consent, forexample, as a transactional agreement where the data subject is alreadyidentified or identifiable as part of the data processing that resultsfrom the provided consent. In any embodiment described herein, thesystem may be configured to generate a consent receipt in response to adata subject providing valid consent. In some embodiments, the system isconfigured to determine whether one or more conditions for valid consenthave been met prior to generating the consent receipt. Variousembodiments of a consent receipt management system are described morefully below.

Exemplary Technical Platforms

As will be appreciated by one skilled in the relevant field, the presentinvention may be, for example, embodied as a computer system, a method,or a computer program product. Accordingly, various embodiments may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, or an embodiment combining software and hardware aspects.Furthermore, particular embodiments may take the form of a computerprogram product stored on a computer-readable storage medium havingcomputer-readable instructions (e.g., software) embodied in the storagemedium. Various embodiments may take the form of web-implementedcomputer software. Any suitable computer-readable storage medium may beutilized including, for example, hard disks, compact disks, DVDs,optical storage devices, and/or magnetic storage devices.

Various embodiments are described below with reference to block diagramsand flowchart illustrations of methods, apparatuses (e.g., systems), andcomputer program products. It should be understood that each block ofthe block diagrams and flowchart illustrations, and combinations ofblocks in the block diagrams and flowchart illustrations, respectively,can be implemented by a computer executing computer programinstructions. These computer program instructions may be loaded onto ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions which execute on the computer or other programmabledata processing apparatus to create means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner such that the instructions stored in the computer-readable memoryproduce an article of manufacture that is configured for implementingthe function specified in the flowchart block or blocks. The computerprogram instructions may also be loaded onto a computer or otherprogrammable data processing apparatus to cause a series of operationalsteps to be performed on the computer or other programmable apparatus toproduce a computer implemented process such that the instructions thatexecute on the computer or other programmable apparatus provide stepsfor implementing the functions specified in the flowchart block orblocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport combinations of mechanisms for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instructions for performing the specified functions. Itshould also be understood that each block of the block diagrams andflowchart illustrations, and combinations of blocks in the blockdiagrams and flowchart illustrations, can be implemented by specialpurpose hardware-based computer systems that perform the specifiedfunctions or steps, or combinations of special purpose hardware andother hardware executing appropriate computer instructions.

Example System Architecture

FIG. 1 is a block diagram of a Data Model Generation and PopulationSystem 100 according to a particular embodiment. In various embodiments,the Data Model Generation and Population System 100 is part of a privacycompliance system (also referred to as a privacy management system), orother system, which may, for example, be associated with a particularorganization and be configured to aid in compliance with one or morelegal or industry regulations related to the collection and storage ofpersonal data. In some embodiments, the Data Model Generation andPopulation System 100 is configured to: (1) generate a data model basedon one or more identified data assets, where the data model includes adata inventory associated with each of the one or more identified dataassets; (2) identify populated and unpopulated aspects of each datainventory; and (3) populate the unpopulated aspects of each datainventory using one or more techniques such as intelligent identityscanning, questionnaire response mapping, APIs, etc.

As may be understood from FIG. 1, the Data Model Generation andPopulation System 100 includes one or more computer networks 115, a DataModel Generation Server 110, a Data Model Population Server 120, anIntelligent Identity Scanning Server 130, One or More Databases 140 orother data structures, one or more remote computing devices 150 (e.g., adesktop computer, laptop computer, tablet computer, smartphone, etc.),and One or More Third Party Servers 160. In particular embodiments, theone or more computer networks 115 facilitate communication between theData Model Generation Server 110, Data Model Population Server 120,Intelligent Identity Scanning Server 130, One or More Databases 140, oneor more remote computing devices 150 (e.g., a desktop computer, laptopcomputer, tablet computer, smartphone, etc.), and One or More ThirdParty Servers 160. Although in the embodiment shown in FIG. 1, the DataModel Generation Server 110, Data Model Population Server 120,Intelligent Identity Scanning Server 130, One or More Databases 140, oneor more remote computing devices 150 (e.g., a desktop computer, laptopcomputer, tablet computer, smartphone, etc.), and One or More ThirdParty Servers 160 are shown as separate servers, it should be understoodthat in other embodiments, one or more of these servers and/or computingdevices may comprise a single server, a plurality of servers, one ormore cloud-based servers, or any other suitable configuration.

The one or more computer networks 115 may include any of a variety oftypes of wired or wireless computer networks such as the Internet, aprivate intranet, a public switch telephone network (PSTN), or any othertype of network. The communication link between The Intelligent IdentityScanning Server 130 and the One or More Third Party Servers 160 may be,for example, implemented via a Local Area Network (LAN) or via theInternet. In other embodiments, the One or More Databases 140 may bestored either fully or partially on any suitable server or combinationof servers described herein.

FIG. 2 illustrates a diagrammatic representation of a computer 200 thatcan be used within the Data Model Generation and Population System 100,for example, as a client computer (e.g., one or more remote computingdevices 130 shown in FIG. 1), or as a server computer (e.g., Data ModelGeneration Server 110 shown in FIG. 1). In particular embodiments, thecomputer 200 may be suitable for use as a computer within the context ofthe Data Model Generation and Population System 100 that is configuredto generate a data model and map one or more relationships between oneor more pieces of data that make up the model.

In particular embodiments, the computer 200 may be connected (e.g.,networked) to other computers in a LAN, an intranet, an extranet, and/orthe Internet. As noted above, the computer 200 may operate in thecapacity of a server or a client computer in a client-server networkenvironment, or as a peer computer in a peer-to-peer (or distributed)network environment. The Computer 200 may be a personal computer (PC), atablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), acellular telephone, a web appliance, a server, a network router, aswitch or bridge, or any other computer capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that computer. Further, while only a single computer is illustrated,the term “computer” shall also be taken to include any collection ofcomputers that individually or jointly execute a set (or multiple sets)of instructions to perform any one or more of the methodologiesdiscussed herein.

An exemplary computer 200 includes a processing device 202, a mainmemory 204 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc.), static memory 206 (e.g., flash memory, static randomaccess memory (SRAM), etc.), and a data storage device 218, whichcommunicate with each other via a bus 232.

The processing device 202 represents one or more general-purposeprocessing devices such as a microprocessor, a central processing unit,or the like. More particularly, the processing device 202 may be acomplex instruction set computing (CISC) microprocessor, reducedinstruction set computing (RISC) microprocessor, very long instructionword (VLIW) microprocessor, or processor implementing other instructionsets, or processors implementing a combination of instruction sets. Theprocessing device 202 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor, or the like. The processing device 202 may beconfigured to execute processing logic 226 for performing variousoperations and steps discussed herein.

The computer 120 may further include a network interface device 208. Thecomputer 200 also may include a video display unit 210 (e.g., a liquidcrystal display (LCD) or a cathode ray tube (CRT)), an alphanumericinput device 212 (e.g., a keyboard), a cursor control device 214 (e.g.,a mouse), and a signal generation device 216 (e.g., a speaker).

The data storage device 218 may include a non-transitorycomputer-accessible storage medium 230 (also known as a non-transitorycomputer-readable storage medium or a non-transitory computer-readablemedium) on which is stored one or more sets of instructions (e.g.,software instructions 222) embodying any one or more of themethodologies or functions described herein. The software instructions222 may also reside, completely or at least partially, within mainmemory 204 and/or within processing device 202 during execution thereofby computer 200—main memory 204 and processing device 202 alsoconstituting computer-accessible storage media. The softwareinstructions 222 may further be transmitted or received over a network115 via network interface device 208.

While the computer-accessible storage medium 230 is shown in anexemplary embodiment to be a single medium, the term“computer-accessible storage medium” should be understood to include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore sets of instructions. The term “computer-accessible storage medium”should also be understood to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by thecomputer and that cause the computer to perform any one or more of themethodologies of the present invention. The term “computer-accessiblestorage medium” should accordingly be understood to include, but not belimited to, solid-state memories, optical and magnetic media, etc.

Exemplary System Platform

Various embodiments of a Data Model Generation and Population System 100may be implemented in the context of any suitable system (e.g., aprivacy compliance system). For example, the Data Model Generation andPopulation System 100 may be implemented to analyze a particular companyor other organization's data assets to generate a data model for one ormore processing activities, privacy campaigns, etc. undertaken by theorganization. In particular embodiments, the system may implement one ormore modules in order to at least partially ensure compliance with oneor more regulations (e.g., legal requirements) related to the collectionand/or storage of personal data. Various aspects of the system'sfunctionality may be executed by certain system modules, including aData Model Generation Module 300, Data Model Population Module 1100,Data Population Questionnaire Generation Module 1200, IntelligentIdentity Scanning Module 2600, and Data Subject Access RequestFulfillment Module 2900. These modules are discussed in greater detailbelow.

Although these modules are presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of theData Model Generation Module 300, Data Model Population Module 1100,Data Population Questionnaire Generation Module 1200, IntelligentIdentity Scanning Module 2600, and Data Subject Access RequestFulfillment Module 2900 described herein may perform the steps describedbelow in an order other than in which they are presented. In still otherembodiments, the Data Model Generation Module 300, Data Model PopulationModule 1100, Data Population Questionnaire Generation Module 1200,Intelligent Identity Scanning Module 2600, and Data Subject AccessRequest Fulfillment Module 2900 may omit certain steps described below.In various other embodiments, the Data Model Generation Module 300, DataModel Population Module 1100, Data Population Questionnaire GenerationModule 1200, Intelligent Identity Scanning Module 2600, and Data SubjectAccess Request Fulfillment Module 2900 may perform steps in addition tothose described (e.g., such as one or more steps described with respectto one or more other modules, etc.).

Data Model Generation Module

In particular embodiments, a Data Model Generation Module 300 isconfigured to: (1) generate a data model (e.g., a data inventory) forone or more data assets utilized by a particular organization; (2)generate a respective data inventory for each of the one or more dataassets; and (3) map one or more relationships between one or moreaspects of the data inventory, the one or more data assets, etc. withinthe data model. In particular embodiments, a data asset (e.g., datasystem, software application, etc.) may include, for example, any entitythat collects, processes, contains, and/or transfers data (e.g., such asa software application, “internet of things” computerized device,database, website, data-center, server, etc.). For example, a first dataasset may include any software or device (e.g., server or servers)utilized by a particular entity for such data collection, processing,transfer, storage, etc.

In particular embodiments, a particular data asset, or collection ofdata assets, may be utilized as part of a particular data processingactivity (e.g., direct deposit generation for payroll purposes). Invarious embodiments, a data model generation system may, on behalf of aparticular organization (e.g., entity), generate a data model thatencompasses a plurality of processing activities. In other embodiments,the system may be configured to generate a discrete data model for eachof a plurality of processing activities undertaken by an organization.

Turning to FIG. 3, in particular embodiments, when executing the DataModel Generation Module 300, the system begins, at Step 310, bygenerating a data model for one or more data assets and digitallystoring the data model in computer memory. The system may, for example,store the data model in the One or More Databases 140 described above(or any other suitable data structure). In various embodiments,generating the data model comprises generating a data structure thatcomprises information regarding one or more data assets, attributes andother elements that make up the data model. As may be understood inlight of this disclosure, the one or more data assets may include anydata assets that may be related to one another. In particularembodiments, the one or more data assets may be related by virtue ofbeing associated with a particular entity (e.g., organization). Forexample, the one or more data assets may include one or more computerservers owned, operated, or utilized by the entity that at leasttemporarily store data sent, received, or otherwise processed by theparticular entity.

In still other embodiments, the one or more data assets may comprise oneor more third party assets which may, for example, send, receive and/orprocess personal data on behalf of the particular entity. These one ormore data assets may include, for example, one or more softwareapplications (e.g., such as Expensify to collect expense information,QuickBooks to maintain and store salary information, etc.).

Continuing to step 320, the system is configured to identify a firstdata asset of the one or more data assets. In particular embodiments,the first data asset may include, for example, any entity (e.g., system)that collects, processes, contains, and/or transfers data (e.g., such asa software application, “interne of things” computerized device,database, website, data-center, server, etc.). For example, the firstdata asset may include any software or device utilized by a particularorganization for such data collection, processing, transfer, etc. Invarious embodiments, the first data asset may be associated with aparticular processing activity (e.g., the first data asset may make upat least a part of a data flow that relates to the collection, storage,transfer, access, use, etc. of a particular piece of data (e.g.,personal data)). Information regarding the first data asset may clarify,for example, one or more relationships between and/or among one or moreother data assets within a particular organization. In a particularexample, the first data asset may include a software applicationprovided by a third party (e.g., a third party vendor) with which theparticular entity interfaces for the purpose of collecting, storing, orotherwise processing personal data (e.g., personal data regardingcustomers, employees, potential customers, etc.).

In particular embodiments, the first data asset is a storage asset thatmay, for example: (1) receive one or more pieces of personal data formone or more collection assets; (2) transfer one or more pieces ofpersonal data to one or more transfer assets; and/or (3) provide accessto one or more pieces of personal data to one or more authorizedindividuals (e.g., one or more employees, managers, or other authorizedindividuals within a particular entity or organization). In a particularembodiment, the first data asset is a primary data asset associated witha particular processing activity around which the system is configuredto build a data model associated with the particular processingactivity.

In particular embodiments, the system is configured to identify thefirst data asset by scanning a plurality of computer systems associatedwith a particular entity (e.g., owned, operated, utilized, etc. by theparticular entity). In various embodiments, the system is configured toidentify the first data asset from a plurality of data assets identifiedin response to completion, by one or more users, of one or morequestionnaires.

Advancing to Step 330, the system generates a first data inventory ofthe first data asset. The data inventory may comprise, for example, oneor more inventory attributes associated with the first data asset suchas, for example: (1) one or more processing activities associated withthe first data asset; (2) transfer data associated with the first dataasset (e.g., how and where the data is being transferred to and/orfrom); (3) personal data associated with the first data asset (e.g.,what type of personal data is collected and/or stored by the first dataasset; how, and from where, the data is collected, etc.); (4) storagedata associated with the personal data (e.g., whether the data is beingstored, protected and deleted); and (5) any other suitable attributerelated to the collection, use, and transfer of personal data. In otherembodiments, the one or more inventory attributes may comprise one ormore other pieces of information such as, for example: (1) the type ofdata being stored by the first data asset; (2) an amount of data storedby the first data asset; (3) whether the data is encrypted; (4) alocation of the stored data (e.g., a physical location of one or morecomputer servers on which the data is stored); etc. In particular otherembodiments, the one or more inventory attributes may comprise one ormore pieces of information technology data related to the first dataasset (e.g., such as one or more pieces of network and/or infrastructureinformation, IP address, MAC address, etc.).

In various embodiments, the system may generate the data inventory basedat least in part on the type of first data asset. For example,particular types of data assets may have particular default inventoryattributes. In such embodiments, the system is configured to generatethe data inventory for the first data asset, which may, for example,include one or more placeholder fields to be populated by the system ata later time. In this way, the system may, for example, identifyparticular inventory attributes for a particular data asset for whichinformation and/or population of data is required as the system buildsthe data model.

As may be understood in light of this disclosure, the system may, whengenerating the data inventory for the first data asset, generate one ormore placeholder fields that may include, for example: (1) theorganization (e.g., entity) that owns and/or uses the first data asset(a primary data asset, which is shown in the center of the data model inFIG. 4); (2) one or more departments within the organization that areresponsible for the first data asset; (3) one or more softwareapplications that collect data (e.g., personal data) for storage inand/or use by the first data asset (e.g., or one or more other suitablecollection assets from which the personal data that is collected,processed, stored, etc. by the first data asset is sourced); (4) one ormore particular data subjects (or categories of data subjects) thatinformation is collected from for use by the first data asset; (5) oneor more particular types of data that are collected by each of theparticular applications for storage in and/or use by the first dataasset; (6) one or more individuals (e.g., particular individuals ortypes of individuals) that are permitted to access and/or use the datastored in, or used by, the first data asset; (7) which particular typesof data each of those individuals are allowed to access and use; and (8)one or more data assets (destination assets) that the data istransferred to from the first data asset, and which particular data istransferred to each of those data assets.

As may be understood in light of this disclosure, the system may beconfigured to generate the one or more placeholder fields based at leastin part on, for example: (1) the type of the first data asset; (2) oneor more third party vendors utilized by the particular organization; (3)a number of collection or storage assets typically associated with thetype of the first data asset; and/or (4) any other suitable factorrelated to the first data asset, its one or more inventory attributes,etc. In other embodiments, the system may substantially automaticallygenerate the one or more placeholders based at least in part on ahierarchy and/or organization of the entity for which the data model isbeing built. For example, a particular entity may have a marketingdivision, legal department, human resources department, engineeringdivision, or other suitable combination of departments that make up anoverall organization. Other particular entities may have furthersubdivisions within the organization. When generating the data inventoryfor the first data asset, the system may identify that the first dataasset will have both an associated organization and subdivision withinthe organization to which it is assigned. In this example, the systemmay be configured to store an indication in computer memory that thefirst data asset is associated with an organization and a departmentwithin the organization.

Next, at Step 340, the system modifies the data model to include thefirst data inventory and electronically links the first data inventoryto the first data asset within the data model. In various embodiments,modifying the data model may include configuring the data model to storethe data inventory in computer memory, and to digitally associate thedata inventory with the first data asset in memory.

FIGS. 4 and 5 show a data model according to a particular embodiment. Asshown in these figures, the data model may store the followinginformation for the first data asset: (1) the organization that ownsand/or uses the first data asset; (2) one or more departments within theorganization that are responsible for the first data asset; (3) one ormore applications that collect data (e.g., personal data) for storage inand/or use by the first data asset; (4) one or more particular datasubjects that information is collected from for use by the first dataasset; (5) one or more collection assets from which the first assetreceives data (e.g., personal data); (6) one or more particular types ofdata that are collected by each of the particular applications (e.g.,collection assets) for storage in and/or use by the first data asset;(7) one or more individuals (e.g., particular individuals, types ofindividuals, or other parties) that are permitted to access and/or usethe data stored in or used by the first data asset; (8) which particulartypes of data each of those individuals are allowed to access and use;and (9) one or more data assets (destination assets) the data istransferred to for other use, and which particular data is transferredto each of those data assets. As shown in FIGS. 6 and 7, the system mayalso optionally store information regarding, for example, which businessprocesses and processing activities utilize the first data asset.

As noted above, in particular embodiments, the data model stores thisinformation for each of a plurality of different data assets and mayinclude one or more links between, for example, a portion of the modelthat provides information for a first particular data asset and a secondportion of the model that provides information for a second particulardata asset.

Advancing to Step 350, the system next identifies a second data assetfrom the one or more data assets. In various embodiments, the seconddata asset may include one of the one or more inventory attributesassociated with the first data asset (e.g., the second data asset mayinclude a collection asset associated with the first data asset, adestination asset or transfer asset associated with the first dataasset, etc.). In various embodiments, as may be understood in light ofthe exemplary data models described below, a second data asset may be aprimary data asset for a second processing activity, while the firstdata asset is the primary data asset for a first processing activity. Insuch embodiments, the second data asset may be a destination asset forthe first data asset as part of the first processing activity. Thesecond data asset may then be associated with one or more seconddestination assets to which the second data asset transfers data. Inthis way, particular data assets that make up the data model may defineone or more connections that the data model is configured to map andstore in memory.

Returning to Step 360, the system is configured to identify one or moreattributes associated with the second data asset, modify the data modelto include the one or more attributes, and map the one or moreattributes of the second data asset within the data model. The systemmay, for example, generate a second data inventory for the second dataasset that comprises any suitable attribute described with respect tothe first data asset above. The system may then modify the data model toinclude the one or more attributes and store the modified data model inmemory. The system may further, in various embodiments, associate thefirst and second data assets in memory as part of the data model. Insuch embodiments, the system may be configured to electronically linkthe first data asset with the second data asset. In various embodiments,such association may indicate a relationship between the first andsecond data assets in the context of the overall data model (e.g.,because the first data asset may serve as a collection asset for thesecond data asset, etc.).

Next, at Step 370, the system may be further configured to generate avisual representation of the data model. In particular embodiments, thevisual representation of the data model comprises a data map. The visualrepresentation may, for example, include the one or more data assets,one or more connections between the one or more data assets, the one ormore inventory attributes, etc.

In particular embodiments, generating the visual representation (e.g.,visual data map) of a particular data model (e.g., data inventory) mayinclude, for example, generating a visual representation that includes:(1) a visual indication of a first data asset (e.g., a storage asset), asecond data asset (e.g., a collection asset), and a third data asset(e.g., a transfer asset); (2) a visual indication of a flow of data(e.g., personal data) from the second data asset to the first data asset(e.g., from the collection asset to the storage asset); (3) a visualindication of a flow of data (e.g., personal data) from the first dataasset to the third data asset (e.g., from the storage asset to thetransfer asset); (4) one or more visual indications of a risk levelassociated with the transfer of personal data; and/or (5) any othersuitable information related to the one or more data assets, thetransfer of data between/among the one or more data assets, access todata stored or collected by the one or more data assets, etc.

In particular embodiments, the visual indication of a particular assetmay comprise a box, symbol, shape, or other suitable visual indicator.In particular embodiments, the visual indication may comprise one ormore labels (e.g., a name of each particular data asset, a type of theasset, etc.). In still other embodiments, the visual indication of aflow of data may comprise one or more arrows. In particular embodiments,the visual representation of the data model may comprise a data flow,flowchart, or other suitable visual representation.

In various embodiments, the system is configured to display (e.g., to auser) the generated visual representation of the data model on asuitable display device.

Exemplary Data Models and Visual Representations of Data Models (e.g.,Data Maps)

FIGS. 4-10 depict exemplary data models according to various embodimentsof the system described herein. FIG. 4, for example, depicts anexemplary data model that does not include a particular processingactivity (e.g., that is not associated with a particular processingactivity). As may be understood from the data model shown in thisfigure, a particular data asset (e.g., a primary data asset) may beassociated with a particular company (e.g., organization), ororganization within a particular company, sub-organization of aparticular organization, etc. In still other embodiments, the particularasset may be associated with one or more collection assets (e.g., one ormore data subjects from whom personal data is collected for storage bythe particular asset), one or more parties that have access to datastored by the particular asset, one or more transfer assets (e.g., oneor more assets to which data stored by the particular asset may betransferred), etc.

As may be understood from FIG. 4, a particular data model for aparticular asset may include a plurality of data elements. Whengenerating the data model for the particular asset, a system may beconfigured to substantially automatically identify one or more types ofdata elements for inclusion in the data model, and automaticallygenerate a data model that includes those identified data elements(e.g., even if one or more of those data elements must remainunpopulated because the system may not initially have access to a valuefor the particular data element). In such cases, the system may beconfigured to store a placeholder for a particular data element untilthe system is able to populate the particular data element with accuratedata.

As may be further understood from FIG. 4, the data model shown in FIG. 4may represent a portion of an overall data model. For example, in theembodiment shown in this figure, the transfer asset depicted may serveas a storage asset for another portion of the data model. In suchembodiments, the transfer asset may be associated with a respective oneor more of the types of data elements described above. In this way, thesystem may generate a data model that may build upon itself to comprisea plurality of layers as the system adds one or more new data assets,attributes, etc.

As may be further understood from FIG. 4, a particular data model mayindicate one or more parties that have access to and/or use of theprimary asset (e.g., storage asset). In such embodiments, the system maybe configured to enable the one or more parties to access one or morepieces of data (e.g., personal data) stored by the storage asset.

As shown in FIG. 4, the data model may further comprise one or morecollection assets (e.g., one or more data assets or individuals fromwhich the storage asset receives data such as personal data). In theexemplary data model (e.g., visual data map) shown in this figure, thecollection assets comprise a data subject (e.g., an individual that mayprovide data to the system for storage in the storage asset) and acollection asset (e.g., which may transfer one or more pieces of datathat the collection asset has collected to the storage asset).

FIG. 5 depicts a portion of an exemplary data model that is populatedfor the primary data asset Gusto. Gusto is a software application that,in the example shown in FIG. 5, may serve as a human resources servicethat contains financial, expense, review, time and attendance,background, and salary information for one or more employees of aparticular organization (e.g., GeneriTech). In the example of FIG. 5,the primary asset (e.g., Gusto) may be utilized by the HR (e.g., HumanResources) department of the particular organization (e.g., GeneriTech).Furthermore, the primary asset, Gusto, may collect financial informationfrom one or more data subjects (e.g., employees of the particularorganization), receive expense information transferred from Expensify(e.g., expensing software), and receive time and attendance datatransferred from Kronos (e.g., timekeeping software). In the exampleshown in FIG. 5, access to the information collected and/or stored byGusto may include, for example: (1) an ability to view and administersalary and background information by HR employees, and (2) an ability toview and administer employee review information by one or more servicemanagers. In the example shown in this figure, personal and other datacollected and stored by Gusto (e.g., salary information, etc.) may betransferred to a company banking system, to QuickBooks, and/or to an HRfile cabinet.

As may be understood from the example shown in FIG. 5, the system may beconfigured to generate a data model based around Gusto that illustratesa flow of personal data utilized by Gusto. The data model in thisexample illustrates, for example, a source of personal data collected,stored and/or processed by Gusto, a destination of such data, anindication of who has access to such data within Gusto, and anorganization and department responsible for the information collected byGusto. In particular embodiments, the data model and accompanying visualrepresentation (e.g., data map) generated by the system as described inany embodiment herein may be utilized in the context of compliance withone or more record keeping requirements related to the collection,storage, and processing of personal data.

FIGS. 6 and 7 depict an exemplary data model and related example that issimilar, in some respects, to the data model and example of FIGS. 4 and5. In the example shown in FIGS. 6 and 7, the exemplary data model andrelated example include a specific business process and processingactivity that is associated with the primary asset (Gusto). In thisexample, the business process is compensation and the specificprocessing activity is direct deposit generation in Gusto. As may beunderstood from this figure, the collection and transfer of data relatedto the storage asset of Gusto is based on a need to generate directdeposits through Gusto in order to compensate employees. Gusto generatesthe information needed to conduct a direct deposit (e.g., financial andsalary information) and then transmits this information to: (1) acompany bank system for execution of the direct deposit; (2) Quickbooksfor use in documenting the direct deposit payment; and (3) HR Filecabinet for use in documenting the salary info and other financialinformation.

As may be understood in light of this disclosure, when generating such adata model, particular pieces of data (e.g., data attributes, dataelements) may not be readily available to the system. In suchembodiment, the system is configured to identify a particular type ofdata, create a placeholder for such data in memory, and seek out (e.g.,scan for and populate) an appropriate piece of data to further populatethe data model. For example, in particular embodiments, the system mayidentify Gusto as a primary asset and recognize that Gusto storesexpense information. The system may then be configured to identify asource of the expense information (e.g., Expensify).

FIG. 8 depicts an exemplary screen display 800 that illustrates a visualrepresentation (e.g., visual data map) of a data model (e.g., a datainventory). In the example shown in FIG. 8, the data map provides avisual indication of a flow of data collected from particular datasubjects (e.g., employees 801). As may be understood from this figure,the data map illustrates that three separate data assets receive data(e.g., which may include personal data) directly from the employees 801.In this example, these three data assets include Kronos 803 (e.g., ahuman resources software application), Workday 805 (e.g., a humanresources software application), and ADP 807 (e.g., a human resourcessoftware application and payment processor). As shown in FIG. 8, thetransfer of data from the employees 801 to these assets is indicated byrespective arrows.

As further illustrated in FIG. 8, the data map indicates a transfer ofdata from Workday 805 to ADP 807 as well as to a Recovery Datacenter 809and a London HR File Center 811. As may be understood in light of thisdisclosure, the Recovery Datacenter 809 and London HR File Center 811may comprise additional data assets in the context of the data modelillustrated by the data map shown in FIG. 8. The Recover Datacenter 809may include, for example, one or more computer servers (e.g., backupservers). The London HR File Center 811 may include, for example, one ormore databases (e.g., such as the One or More Databases 140 shown inFIG. 1). AS shown in FIG. 8, each particular data asset depicted in thedata map may be shown along with a visual indication of the type of dataasset. For example, Kronos 803, Workday 805, and ADP 807 are depictedadjacent a first icon type (e.g., a computer monitor), while RecoverDatacenter 809 and London HR File Center 811 are depicted adjacent asecond and third icon type respectively (e.g., a server cluster and afile folder). In this way, the system may be configured to visuallyindicate, via the data model, particular information related to the datamodel in a relatively minimal manner.

FIG. 9 depicts an exemplary screen display 900 that illustrates a datamap of a plurality of assets 905 in tabular form (e.g., table form). Asmay be understood from this figure, a table that includes one or moreinventory attributes of each particular asset 905 in the table mayindicate, for example: (1) a managing organization 910 of eachrespective asset 905; (2) a hosting location 915 of each respectiveasset 905 (e.g., a physical storage location of each asset 905); (3) atype 920 of each respective asset 905, if known (e.g., a database,software application, server, etc.); (4) a processing activity 925associated with each respective asset 905; and/or (5) a status 930 ofeach particular data asset 905. In various embodiments, the status 930of each particular asset 905 may indicate a status of the asset 905 inthe discovery process. This may include, for example: (1) a “new” statusfor a particular asset that has recently been discovered as an assetthat processes, stores, or collects personal data on behalf of anorganization (e.g., discovered via one or more suitable techniquesdescribed herein); (2) an “in discovery” status for a particular assetfor which the system is populating or seeking to populate one or moreinventory attributes, etc.

FIG. 10 depicts an exemplary data map 1000 that includes an asset map ofa plurality of data assets 1005A-F, which may, for example, be utilizedby a particular entity in the collection, storage, and/or processing ofpersonal data. As may be understood in light of this disclosure, theplurality of data assets 1005A-F may have been discovered using anysuitable technique described herein (e.g., one or more intelligentidentity scanning techniques, one or more questionnaires, one or moreapplication programming interfaces, etc.). In various embodiments, adata inventory for each of the plurality of data assets 1005A-F maydefine, for each of the plurality of data assets 1005A-F a respectiveinventory attribute related to a storage location of the data asset.

As may be understood from this figure, the system may be configured togenerate a map that indicates a location of the plurality of data assets1005A-F for a particular entity. In the embodiment shown in this figure,locations that contain a data asset are indicated by circular indiciathat contain the number of assets present at that location. In theembodiment shown in this figure, the locations are broken down bycountry. In particular embodiments, the asset map may distinguishbetween internal assets (e.g., first party servers, etc.) andexternal/third party assets (e.g., third party owned servers or softwareapplications that the entity utilizes for data storage, transfer, etc.).

In some embodiments, the system is configured to indicate, via thevisual representation, whether one or more assets have an unknownlocation (e.g., because the data model described above may be incompletewith regard to the location). In such embodiments, the system may beconfigured to: (1) identify the asset with the unknown location; (2) useone or more data modeling techniques described herein to determine thelocation (e.g., such as pinging the asset, generating one or morequestionnaires for completion by a suitable individual, etc.); and (3)update a data model associated with the asset to include the location.

Data Model Population Module

In particular embodiments, a Data Model Population Module 1100 isconfigured to: (1) determine one or more unpopulated inventoryattributes in a data model; (2) determine one or more attribute valuesfor the one or more unpopulated inventory attributes; and (3) modify thedata model to include the one or more attribute values.

Turning to FIG. 11, in particular embodiments, when executing the DataModel Population Module 1100, the system begins, at Step 1110, byanalyzing one or more data inventories for each of the one or more dataassets in the data model. The system may, for example, identify one ormore particular data elements (e.g., inventory attributes) that make upthe one or more data inventories. The system may, in variousembodiments, scan one or more data structures associated with the datamodel to identify the one or more data inventories. In variousembodiments, the system is configured to build an inventory of existing(e.g., known) data assets and identify inventory attributes for each ofthe known data assets.

Continuing to Step 1120, the system is configured to determine, for eachof the one or more data inventories, one or more populated inventoryattributes and one or more unpopulated inventory attributes (e.g.,and/or one or more unpopulated data assets within the data model). As aparticular example related to an unpopulated data asset, when generatingand populating a data model, the system may determine that, for aparticular asset, there is a destination asset. In various embodiments,the destination asset may be known (e.g., and already stored by thesystem as part of the data model). In other embodiments, the destinationasset may be unknown (e.g., a data element that comprises thedestination asset may comprise a placeholder or other indication inmemory for the system to populate the unpopulated inventory attribute(e.g., data element).

As another particular example, a particular storage asset may beassociated with a plurality of inventory assets (e.g., stored in a datainventory associated with the storage asset). In this example, theplurality of inventory assets may include an unpopulated inventoryattribute related to a type of personal data stored in the storageasset. The system may, for example, determine that the type of personaldata is an unpopulated inventory asset for the particular storage asset.

Returning to Step 1130, the system is configured to determine, for eachof the one or more unpopulated inventory attributes, one or moreattribute values. In particular embodiments, the system may determinethe one or more attribute values using any suitable technique (e.g., anysuitable technique for populating the data model). In particularembodiments, the one or more techniques for populating the data modelmay include, for example: (1) obtaining data for the data model by usingone or more questionnaires associated with a particular privacycampaign, processing activity, etc.; (2) using one or more intelligentidentity scanning techniques discussed herein to identify personal datastored by the system and then map such data to a suitable data model;(3) using one or more application programming interfaces (API) to obtaindata for the data model from another software application; and/or (4)using any other suitable technique. Exemplary techniques for determiningthe one or more attribute values are described more fully below. Inother embodiments, the system may be configured to use such techniquesor other suitable techniques to populate one or more unpopulated dataassets within the data model.

Next, at Step 1140, the system modifies the data model to include theone or more attribute values for each of the one or more unpopulatedinventory attributes. The system may, for example, store the one or moreattributes values in computer memory, associate the one or moreattribute values with the one or more unpopulated inventory attributes,etc. In still other embodiments, the system may modify the data model toinclude the one or more data assets identified as filling one or morevacancies left within the data model by the unpopulated one or more dataassets.

Continuing to Step 1150, the system is configured to store the modifieddata model in memory. In various embodiments, the system is configuredto store the modified data model in the One or More Databases 140, or inany other suitable location. In particular embodiments, the system isconfigured to store the data model for later use by the system in theprocessing of one or more data subject access requests. In otherembodiments, the system is configured to store the data model for use inone or more privacy impact assessments performed by the system.

Data Model Population Questionnaire Generation Module

In particular embodiments, a Data Population Questionnaire GenerationModule 1200 is configured to generate a questionnaire (e.g., one or morequestionnaires) comprising one or more questions associated with one ormore particular unpopulated data attributes, and populate theunpopulated data attributes based at least in part on one or moreresponses to the questionnaire. In other embodiments, the system may beconfigured to populate the unpopulated data attributes based on one ormore responses to existing questionnaires.

In various embodiments, the one or more questionnaires may comprise oneor more processing activity questionnaires (e.g., privacy impactassessments, data privacy impact assessments, etc.) configured to elicitone or more pieces of data related to one or more undertakings by anorganization related to the collection, storage, and/or processing ofpersonal data (e.g., processing activities). In particular embodiments,the system is configured to generate the questionnaire (e.g., aquestionnaire template) based at least in part on one or more processingactivity attributes, data asset attributes (e.g., inventory attributes),or other suitable attributes discussed herein.

Turning to FIG. 12, in particular embodiments, when executing the DataPopulation Questionnaire Generation Module 1200, the system begins, atStep 1210, by identifying one or more unpopulated data attributes from adata model. The system may, for example, identify the one or moreunpopulated data attributes using any suitable technique describedabove. In particular embodiments, the one or more unpopulated dataattributes may relate to, for example, one or more processing activityor asset attributes such as: (1) one or more processing activitiesassociated with a particular data asset; (2) transfer data associatedwith the particular data asset (e.g., how and where the data storedand/or collected by the particular data asset is being transferred toand/or from); (3) personal data associated with the particular dataassets asset (e.g., what type of personal data is collected and/orstored by the particular data asset; how, and from where, the data iscollected, etc.); (4) storage data associated with the personal data(e.g., whether the data is being stored, protected and deleted); and (5)any other suitable attribute related to the collection, use, andtransfer of personal data by one or more data assets or via one or moreprocessing activities. In other embodiments, the one or more unpopulatedinventory attributes may comprise one or more other pieces ofinformation such as, for example: (1) the type of data being stored bythe particular data asset; (2) an amount of data stored by theparticular data asset; (3) whether the data is encrypted by theparticular data asset; (4) a location of the stored data (e.g., aphysical location of one or more computer servers on which the data isstored by the particular data asset); etc.

Continuing to Step 1220, the system generates a questionnaire (e.g., aquestionnaire template) comprising one or more questions associated withone or more particular unpopulated data attributes. As may be understoodin light of the above, the one or more particulate unpopulated dataattributes may relate to, for example, a particular processing activityor a particular data asset (e.g., a particular data asset utilized aspart of a particular processing activity). In various embodiments, theone or more questionnaires comprise one or more questions associatedwith the unpopulated data attribute. For example, if the data modelincludes an unpopulated data attribute related to a location of a serveron which a particular asset stores personal data, the system maygenerate a questionnaire associated with a processing activity thatutilizes the asset (e.g., or a questionnaire associated with the asset).The system may generate the questionnaire to include one or morequestions regarding the location of the server.

Returning to Step 1230, the system maps one or more responses to the oneor more questions to the associated one or more particular unpopulateddata attributes. The system may, for example, when generating thequestionnaire, associate a particular question with a particularunpopulated data attribute in computer memory. In various embodiments,the questionnaire may comprise a plurality of question/answer pairings,where the answer in the question/answer pairings maps to a particularinventory attribute for a particular data asset or processing activity.

In this way, the system may, upon receiving a response to the particularquestion, substantially automatically populate the particularunpopulated data attribute. Accordingly, at Step 1240, the systemmodifies the data model to populate the one or more responses as one ormore data elements for the one or more particular unpopulated dataattributes. In particular embodiments, the system is configured tomodify the data model such that the one or more responses are stored inassociation with the particular data element (e.g., unpopulated dataattribute) to which the system mapped it at Step 1230. In variousembodiments, the system is configured to store the modified data modelin the One or More Databases 140, or in any other suitable location. Inparticular embodiments, the system is configured to store the data modelfor later use by the system in the processing of one or more datasubject access requests. In other embodiments, the system is configuredto store the data model for use in one or more privacy impactassessments performed by the system.

Continuing to optional Step 1250, the system may be configured to modifythe questionnaire based at least in part on the one or more responses.The system may, for example, substantially dynamically add and/or removeone or more questions to/from the questionnaire based at least in parton the one or more responses (e.g., one or more response received by auser completing the questionnaire). For example, the system may, inresponse to the user providing a particular inventory attribute or newasset, generates additional questions that relate to that particularinventory attribute or asset. The system may, as the system addsadditional questions, substantially automatically map one or moreresponses to one or more other inventory attributes or assets. Forexample, in response to the user indicating that personal data for aparticular asset is stored in a particular location, the system maysubstantially automatically generate one or more additional questionsrelated to, for example, an encryption level of the storage, who hasaccess to the storage location, etc.

In still other embodiments, the system may modify the data model toinclude one or more additional assets, data attributes, inventoryattributes, etc. in response to one or more questionnaire responses. Forexample, the system may modify a data inventory for a particular assetto include a storage encryption data element (which specifies whetherthe particular asset stores particular data in an encrypted format) inresponse to receiving such data from a questionnaire. Modification of aquestionnaire is discussed more fully below with respect to FIG. 13.

Data Model Population via Questionnaire Process Flow

FIG. 13 depicts an exemplary process flow 1300 for populating a datamodel (e.g., modifying a data model to include a newly discovered dataasset, populating one or more inventory attributes for a particularprocessing activity or data asset, etc.). In particular, FIG. 13 depictsone or more exemplary data relationships between one or more particulardata attributes (e.g., processing activity attributes and/or assetattributes), a questionnaire template (e.g., a processing activitytemplate and/or a data asset template), a completed questionnaire (e.g.,a processing activity assessment and/or a data asset assessment), and adata inventory (e.g., a processing activity inventory and/or an assetinventory). As may be understood from this figure the system isconfigured to: (1) identify new data assets; (2) generate an assetinventory for identified new data assets; and (3) populate the generatedasset inventories. Systems and methods for populating the generatedinventories are described more fully below.

As may be understood from FIG. 13, a system may be configured to mapparticular processing activity attributes 1320A to each of: (1) aprocessing activity template 1330A; and (2) a processing activity datainventory 1310A. As may be understood in light of this disclosure, theprocessing activity template 1330A may comprise a plurality of questions(e.g., as part of a questionnaire), which may, for example, beconfigured to elicit discovery of one or more new data assets. Theplurality of questions may each correspond to one or more fields in theprocessing activity inventory 1310A, which may, for example, define oneor more inventory attributes of the processing activity.

In particular embodiments, the system is configured to provide aprocessing activity assessment 1340A to one or more individuals forcompletion. As may be understood from FIG. 13, the system is configuredto launch the processing activity assessment 1340A from the processingactivity inventory 1310A and further configured to create the processingactivity assessment 1340A from the processing activity template 1330.The processing activity assessment 1340A may comprise, for example, oneor more questions related to the processing activity. The system may, invarious embodiments, be configured to map one or more responses providedin the processing activity assessment 1340A to one or more correspondingfields in the processing activity inventory 1310A. The system may thenbe configured to modify the processing activity inventory 1310A toinclude the one or more responses, and store the modified inventory incomputer memory. In various embodiments, the system may be configured toapprove a processing activity assessment 1340A (e.g., receive approvalof the assessment) prior to feeding the processing activity inventoryattribute values into one or more fields and/or cells of the inventory.

As may be further understood from FIG. 13, in response to creating a newasset record (e.g., which the system may create, for example, inresponse to a new asset discovery via the processing activity assessment1340A described immediately above, or in any other suitable manner), thesystem may generate an asset inventory 1310B (e.g., a data assetinventory) that defines a plurality of inventory attributes for the newasset (e.g., new data asset).

As may be understood from FIG. 13, a system may be configured to mapparticular asset attributes 1320B to each of: (1) an asset template1330BA; and (2) an asset inventory 1310A. As may be understood in lightof this disclosure, the asset template 1330B may comprise a plurality ofquestions (e.g., as part of a questionnaire), which may, for example, beconfigured to elicit discovery of one or more processing activitiesassociated with the asset and/or one or more inventory attributes of theasset. The plurality of questions may each correspond to one or morefields in the asset inventory 1310B, which may, for example, define oneor more inventory attributes of the asset.

In particular embodiments, the system is configured to provide an assetassessment 1340B to one or more individuals for completion. As may beunderstood from FIG. 13, the system is configured to launch the assetassessment 1340B from the asset inventory 1310B and further configuredto create the asset assessment 1340B from the asset template 1330B. Theasset assessment 1340B may comprise, for example, one or more questionsrelated to the data asset. The system may, in various embodiments, beconfigured to map one or more responses provided in the asset assessment1340B to one or more corresponding fields in the asset inventory 1310B.The system may then be configured to modify the asset inventory 1310B(e.g., and/or a related processing activity inventory 1310A) to includethe one or more responses, and store the modified inventory in computermemory. In various embodiments, the system may be configured to approvean asset assessment 1340B (e.g., receive approval of the assessment)prior to feeding the asset inventory attribute values into one or morefields and/or cells of the inventory.

FIG. 13 further includes a detail view 1350 of a relationship betweenparticular data attributes 1320C with an exemplary data inventory 1310Cand a questionnaire template 1330C. As may be understood from thisdetail view 1350, a particular attribute name may map to a particularquestion title in a template 1330C as well as to a field name in anexemplary data inventory 1310C. In this way, the system may beconfigured to populate (e.g., automatically populate) a field name for aparticular inventory 1310C in response to a user providing a questiontitle as part of a questionnaire template 1330C. Similarly, a particularattribute description may map to a particular question description in atemplate 1330C as well as to a tooltip on a fieldname in an exemplarydata inventory 1310C. In this way, the system may be configured toprovide the tooltip for a particular inventory 1310C that includes thequestion description provided by a user as part of a questionnairetemplate 1330C.

As may be further understood from the detail view 1350 of FIG. 13, aparticular response type may map to a particular question type in atemplate 1330C as well as to a field type in an exemplary data inventory1310C. A particular question type may include, for example, a multiplechoice question (e.g., A, B, C, etc.), a freeform response, an integervalue, a drop down selection, etc. A particular field type may include,for example, a memo field type, a numeric field type, an integer fieldtype, a logical field type, or any other suitable field type. Aparticular data attribute may require a response type of, for example:(1) a name of an organization responsible for a data asset (e.g., a freeform response); (2) a number of days that data is stored by the dataasset (e.g., an integer value); and/or (3) any other suitable responsetype.

In still other embodiments, the system may be configured to map a one ormore attribute values to one or more answer choices in a template 1330Cas well as to one or more lists and/or responses in a data inventory1310C. The system may then be configured to populate a field in the datainventory 1310C with the one or more answer choices provided in aresponse to a question template 1330C with one or more attribute values.

Exemplary Questionnaire Generation and Completion User Experience

FIGS. 14-25 depict exemplary screen displays that a user may encounterwhen generating a questionnaire (e.g., one or more questionnaires and/ortemplates) for populating one or more data elements (e.g., inventoryattributes) of a data model for a data asset and/or processing activity.FIG. 14, for example, depicts an exemplary asset based questionnairetemplate builder 1400. As may be understood from FIG. 14, the templatebuilder may enable a user to generate an asset based questionnairetemplate that includes one or more sections 1420 related to the asset(e.g., asset information, security, disposal, processing activities,etc.). As may be understood in light of this disclosure, the system maybe configured to substantially automatically generate an asset basedquestionnaire template based at least in part on the one or moreunpopulated inventory attributes discussed above. The system may, forexample, be configured to generate a template that is configured topopulate the one or more unpopulated attributes (e.g., by elicitingresponses, via a questionnaire to one or more questions that are mappedto the attributes within the data inventory).

In various embodiments, the system is configured to enable a user tomodify a default template (e.g., or a system-created template) by, forexample, adding additional sections, adding one or more additionalquestions to a particular section, etc. In various embodiments, thesystem may provide one or more tools for modifying the template. Forexample, in the embodiment shown in FIG. 14, the system may provide auser with a draft and drop question template 1410, from which the usermay select a question type (e.g., textbox, multiple choice, etc.).

A template for an asset may include, for example: (1) one or morequestions requesting general information about the asset; (2) one ormore security-related questions about the asset; (3) one or morequestions regarding how the data asset disposes of data that it uses;and/or (4) one or more questions regarding processing activities thatinvolve the data asset. In various embodiments, each of these one ormore sections may comprise one or more specific questions that may mapto particular portions of a data model (e.g., a data map).

FIG. 15 depicts an exemplary screen display of a processing activityquestionnaire template builder 1500. The screen display shown in FIG. 15is similar to the template builder shown in FIG. 14 with respect to thedata asset based template builder. As may be understood from FIG. 15,the template builder may enable a user to generate a processing activitybased questionnaire template that includes one or more sections 1520related to the processing activity (e.g., business process information,personal data, source, storage, destinations, access and use, etc.). Asmay be understood in light of this disclosure, the system may beconfigured to substantially automatically generate a processing activitybased questionnaire template based at least in part on the one or moreunpopulated inventory attributes related to the processing activity(e.g., as discussed above). The system may, for example, be configuredto generate a template that is configured to populate the one or moreunpopulated attributes (e.g., by eliciting responses, via aquestionnaire to one or more questions that are mapped to the attributeswithin the data inventory).

In various embodiments, the system is configured to enable a user tomodify a default template (e.g., or a system-created template) by, forexample, adding additional sections, adding one or more additionalquestions to a particular section, etc. In various embodiments, thesystem may provide one or more tools for modifying the template. Forexample, in the embodiment shown in FIG. 15, the system may provide auser with a draft and drop question template 1510, from which the usermay select a question type (e.g., textbox, multiple choice, assetattributes, data subjects, etc.). The system may be further configuredto enable a user to publish a completed template (e.g., for use in aparticular assessment). In other embodiments, the system may beconfigured to substantially automatically publish the template.

In various embodiments, a template for a processing activity mayinclude, for example: (1) one or more questions related to the type ofbusiness process that involves a particular data asset; (2) one or morequestions regarding what type of personal data is acquired from datasubjects for use by a particular data asset; (3) one or more questionsrelated to a source of the acquired personal data; (4) one or morequestions related to how and/or where the personal data will be storedand/or for how long; (5) one or more questions related to one or moreother data assets that the personal data will be transferred to; and/or(6) one or more questions related to who will have the ability to accessand/or use the personal data.

Continuing to FIG. 16, an exemplary screen display 1600 depicts alisting of assets 1610 for a particular entity. These may, for example,have been identified as part of the data model generation systemdescribed above. As may be understood from this figure, a user mayselect a drop down indicator 1615 to view more information about aparticular asset. In the exemplary embodiment shown in FIG. 16, thesystem stores the managing organization group for the “New Asset”, butis missing some additional information (e.g., such as a description 1625of the asset). In order to fill out the missing inventory attributes forthe “New Asset”, the system, in particular embodiments, is configured toenable a user to select a Send Assessment indicia 1620 in order totransmit an assessment related to the selected asset to an individualtasked with providing one or more pieces of information related to theasset (e.g., a manager, or other individual with knowledge of the one ormore inventory attributes).

In response to the user selecting the Send Assessment indicia 1620, thesystem may create the assessment based at least in part on a templateassociated with the asset, and transmit the assessment to a suitableindividual for completion (e.g., and/or transmit a request to theindividual to complete the assessment).

FIG. 17 depicts an exemplary assessment transmission interface 1700 viawhich a user can transmit one or more assessments for completion. Asshown in this figure, the user may assign a respondent, provide adeadline, indicate a reminder time, and provide one or more commentsusing an assessment request interface 1710. The user may then select aSend Assessment(s) indicia 1720 in order to transmit the assessment.

FIG. 18 depicts an exemplary assessment 1800 which a user may encounterin response to receiving a request to complete the assessment asdescribed above with respect to FIGS. 16 and 17. As shown in FIG. 18,the assessment 1800 may include one or more questions that map to theone or more unpopulated attributes for the asset shown in FIG. 16. Forexample, the one or more questions may include a question related to adescription of the asset, which may include a free form text box 1820for providing a description of the asset. FIG. 19 depicts an exemplaryscreen display 1900 with the text box 1920 completed, where thedescription includes a value of “Value_1”. As shown in FIGS. 18 and 19,the user may have renamed “New Asset” (e.g., which may have included adefault or placeholder name) shown in FIGS. 16 and 17 to “7^(th) Asset.”

Continuing to FIG. 20, the exemplary screen display 2000 depicts thelisting of assets 2010 from FIG. 16 with some additional attributespopulated. For example, the Description 2025 (e.g., “Value_1”) providedin FIG. 19 has been added to the inventory. As may be understood inlight of this disclosure, in response to a user providing thedescription via the assessment shown in FIGS. 18 and 19, the system maybe configured to map the provided description to the attribute valueassociated with the description of the asset in the data inventory. Thesystem may have then modified the data inventory for the asset toinclude the description attribute. In various embodiments, the system isconfigured to store the modified data inventory as part of a data model(e.g., in computer memory).

FIGS. 21-24 depict exemplary screen displays showing exemplary questionsthat make up part of a processing activity questionnaire (e.g.,assessment). FIG. 21 depicts an exemplary interface 2100 for respondingto a first question 2110 and a second question 2120. As shown in FIG.21, the first question 2110 relates to whether the processing activityis a new or existing processing activity. The first question 2110 shownin FIG. 21 is a multiple choice question. The second question 2120relates to whether the organization is conducting the activity on behalfof another organization. As shown in this figure, the second question2120 includes both a multiple choice portion and a free-form responseportion.

As discussed above, in various embodiments, the system may be configuredto modify a questionnaire in response to (e.g., based on) one or moreresponses provided by a user completing the questionnaire. In particularembodiments, the system is configured to modify the questionnairesubstantially on-the-fly (e.g., as the user provides each particularanswer). FIG. 22 depicts an interface 2200 that includes a secondquestion 2220 that differs from the second question 2120 shown in FIG.21. As may be understood in light of this disclosure, in response to theuser providing a response to the first question 2110 in FIG. 21 thatindicates that the processing activity is a new processing activity, thesystem may substantially automatically modify the second question 2120from FIG. 21 to the second question 2220 from FIG. 22 (e.g., such thatthe second question 2220 includes one or more follow up questions orrequests for additional information based on the response to the firstquestion 2110 in FIG. 21).

As shown in FIG. 22, the second question 2220 requests a description ofthe activity that is being pursued. In various embodiments (e.g., suchas if the user had selected that the processing activity was an existingone), the system may not modify the questionnaire to include the secondquestion 2220 from FIG. 22, because the system may already storeinformation related to a description of the processing activity atissue. In various embodiments, any suitable question described hereinmay include a tooltip 2225 on a field name (e.g., which may provide oneor more additional pieces of information to guide a user's response tothe questionnaire and/or assessment).

FIGS. 23 and 24 depict additional exemplary assessment questions. Thequestions shown in these figures relate to, for example, particular dataelements processed by various aspects of a processing activity.

FIG. 25 depicts a dashboard 2500 that includes an accounting of one ormore assessments that have been completed, are in progress, or requirecompletion by a particular organization. The dashboard 2500 shown inthis figure is configured to provide information relate to the status ofone or more outstanding assessments. As may be understood in light ofthis disclosure, because of the volume of assessment requests, it may benecessary to utilize one or more third party organizations to facilitatea timely completion of one or more assessment requests. In variousembodiments, the dashboard may indicate that, based on a fact that anumber of assessments are still in progress or incomplete, that aparticular data model for an entity, data asset, processing activity,etc. remains incomplete. In such embodiments, an incomplete nature of adata model may raise one or more flags or indicate a risk that an entitymay not be in compliance with one or more legal or industry requirementsrelated to the collection, storage, and/or processing of personal data.

Intelligent Identity Scanning Module

Turning to FIG. 26, in particular embodiments, the Intelligent IdentityScanning Module 2600 is configured to scan one or more data sources toidentify personal data stored on one or more network devices for aparticular organization, analyze the identified personal data, andclassify the personal data (e.g., in a data model) based at least inpart on a confidence score derived using one or more machine learningtechniques. The confidence score may be and/or comprise, for example, anindication of the probability that the personal data is actuallyassociated with a particular data subject (e.g., that there is at leastan 80% confidence level that a particular phone number is associatedwith a particular individual.)

When executing the Intelligent Identity Scanning Module 2600, the systembegins, at Step 2610, by connecting to one or more databases or otherdata structures, and scanning the one or more databases to generate acatalog of one or more individuals and one or more pieces of personalinformation associated with the one or more individuals. The system may,for example, be configured to connect to one or more databasesassociated with a particular organization (e.g., one or more databasesthat may serve as a storage location for any personal or other datacollected, processed, etc. by the particular organization, for example,as part of a suitable processing activity. As may be understood in lightof this disclosure, a particular organization may use a plurality of oneor more databases (e.g., the One or More Databases 140 shown in FIG. 1),a plurality of servers (e.g., the One or More Third Party Servers 160shown in FIG. 1), or any other suitable data storage location in orderto store personal data and other data collected as part of any suitableprivacy campaign, privacy impact assessment, processing activity, etc.

In particular embodiments, the system is configured to scan the one ormore databases by searching for particular data fields comprising one ormore pieces of information that may include personal data. The systemmay, for example, be configured to scan and identify one of more piecesof personal data such as: (1) name; (2) address; (3) telephone number;(4) e-mail address; (5) social security number; (6) informationassociated with one or more credit accounts (e.g., credit card numbers);(7) banking information; (8) location data; (9) internet search history;(10) non-credit account data; and/or (11) any other suitable personalinformation discussed herein. In particular embodiments, the system isconfigured to scan for a particular type of personal data (e.g., or oneor more particular types of personal data).

The system may, in various embodiments, be further configured togenerate a catalog of one or more individuals that also includes one ormore pieces of personal information (e.g., personal data) identified forthe individuals during the scan. The system may, for example, inresponse to discovering one or more pieces of personal data in aparticular storage location, identify one or more associations betweenthe discovered pieces of personal data. For example, a particulardatabase may store a plurality of individuals' names in association withtheir respective telephone numbers. One or more other databases mayinclude any other suitable information.

The system may, for example, generate the catalog to include anyinformation associated with the one or more individuals identified inthe scan. The system may, for example, maintain the catalog in anysuitable format (e.g., a data table, etc.).

Continuing to Step 2620, the system is configured to scan one or morestructured and/or unstructured data repositories based at least in parton the generated catalog to identify one or more attributes of dataassociated with the one or more individuals. The system may, forexample, be configured to utilize information discovered during theinitial scan at Step 2610 to identify the one or more attributes of dataassociated with the one or more individuals.

For example, the catalog generated at Step 2610 may include a name,address, and phone number for a particular individual. The system may beconfigured, at Step 2620, to scan the one or more structured and/orunstructured data repositories to identify one or more attributes thatare associated with one or more of the particular individual's name,address and/or phone number. For example, a particular data repositorymay store banking information (e.g., a bank account number and routingnumber for the bank) in association with the particular individual'saddress. In various embodiments, the system may be configured toidentify the banking information as an attribute of data associated withthe particular individual. In this way, the system may be configured toidentify particular data attributes (e.g., one or more pieces ofpersonal data) stored for a particular individual by identifying theparticular data attributes using information other than the individual'sname.

Returning to Step 2630, the system is configured to analyze andcorrelate the one or more attributes and metadata for the scanned one ormore structured and/or unstructured data repositories. In particularembodiments, the system is configured to correlate the one or moreattributes with metadata for the associated data repositories from whichthe system identified the one or more attributes. In this way, thesystem may be configured to store data regarding particular datarepositories that store particular data attributes.

In particular embodiments, the system may be configured tocross-reference the data repositories that are discovered to store oneor more attributes of personal data associated with the one or moreindividuals with a database of known data assets. In particularembodiments, the system is configured to analyze the data repositoriesto determine whether each data repository is part of an existing datamodel of data assets that collect, store, and/or process personal data.In response to determining that a particular data repository is notassociated with an existing data model, the system may be configured toidentify the data repository as a new data asset (e.g., via assetdiscovery), and take one or more actions (e.g., such as any suitableactions described herein) to generate and populate a data model of thenewly discovered data asset. This may include, for example: (1)generating a data inventory for the new data asset; (2) populating thedata inventory with any known attributes associated with the new dataasset; (3) identifying one or more unpopulated (e.g., unknown)attributes of the data asset; and (4) taking any suitable actiondescribed herein to populate the unpopulated data attributes.

In particular embodiments, the system my, for example: (1) identify asource of the personal data stored in the data repository that led tothe new asset discovery; (2) identify one or more relationships betweenthe newly discovered asset and one or more known assets; and/or (3) etc.

Continuing to Step 2640, the system is configured to use one or moremachine learning techniques to categorize one or more data elements fromthe generated catalog, analyze a flow of the data among the one or moredata repositories, and/or classify the one or more data elements basedon a confidence score as discussed below.

Continuing to Step 2650, the system, in various embodiments, isconfigured to receive input from a user confirming or denying acategorization of the one or more data elements, and, in response,modify the confidence score. In various embodiments, the system isconfigured to iteratively repeat Steps 2640 and 2650. In this way, thesystem is configured to modify the confidence score in response to auser confirming or denying the accuracy of a categorization of the oneor more data elements. For example, in particular embodiments, thesystem is configured to prompt a user (e.g., a system administrator,privacy officer, etc.) to confirm that a particular data element is, infact, associated with a particular individual from the catalog. Thesystem may, in various embodiments, be configured to prompt a user toconfirm that a data element or attribute discovered during one or moreof the scans above were properly categorized at Step 2640.

In particular embodiments, the system is configured to modify theconfidence score based at least in part on receiving one or moreconfirmations that one or more particular data elements or attributesdiscovered in a particular location during a scan are associated withparticular individuals from the catalog. As may be understood in lightof this disclosure, the system may be configured to increase theconfidence score in response to receiving confirmation that particulartypes of data elements or attributes discovered in a particular storagelocation are typically confirmed as being associated with particularindividuals based on one or more attributes for which the system wasscanning.

Exemplary Intelligent Identity Scanning Technical Platforms

FIG. 27 depicts an exemplary technical platform via which the system mayperform one or more of the steps described above with respect to theIntelligent Identity Scanning Module 2600. As shown in the embodiment inthis figure, an Intelligent Identity Scanning System 2600 comprises anIntelligent Identity Scanning Server 130, such as the IntelligentIdentity Scanning Server 130 described above with respect to FIG. 1. TheIntelligent Identity Scanning Server 130 may, for example, comprise aprocessing engine (e.g., one or more computer processors). In someembodiments, the Intelligent Identity Scanning Server 130 may includeany suitable cloud hosted processing engine (e.g., one or morecloud-based computer servers). In particular embodiments, theIntelligent Identity Scanning Server 130 is hosted in a Microsoft Azurecloud.

In particular embodiments, the Intelligent Identity Scanning Server 130is configured to sit outside one or more firewalls (e.g., such as thefirewall 195 shown in FIG. 26). In such embodiments, the IntelligentIdentity Scanning Server 130 is configured to access One or More RemoteComputing Devices 150 through the Firewall 195 (e.g., one or morefirewalls) via One or More Networks 115 (e.g., such as any of the One orMore Networks 115 described above with respect to FIG. 1).

In particular embodiments, the One or More Remote Computing Devices 150include one or more computing devices that make up at least a portion ofone or more computer networks associated with a particular organization.In particular embodiments, the one or more computer networks associatedwith the particular organization comprise one or more suitable servers,one or more suitable databases, one or more privileged networks, and/orany other suitable device and/or network segment that may store and/orprovide for the storage of personal data. In the embodiment shown inFIG. 27, the one or more computer networks associated with theparticular organization may comprise One or More Third Party Servers160, One or More Databases 140, etc. In particular embodiments, the Oneor More Remote Computing Devices 150 are configured to access one ormore segments of the one or more computer networks associated with theparticular organization. In some embodiments, the one or more computernetworks associated with the particular organization comprise One orMore Privileged Networks 165. In still other embodiments, the one ormore computer networks comprise one or more network segments connectedvia one or more suitable routers, one or more suitable network hubs, oneor more suitable network switches, etc.

As shown in FIG. 27, various components that make up one or more partsof the one or more computer networks associated with the particularorganization may store personal data (e.g., such as personal data storedon the One or More Third Party Servers 160, the One or More Databases140, etc.). In various embodiments, the system is configured to performone or more steps related to the Intelligent Identity Scanning Server2600 in order to identify the personal data for the purpose ofgenerating the catalog of individuals described above (e.g., and/oridentify one or more data assets within the organization's network thatstore personal data)

As further shown in FIG. 27, in various embodiments, the One or MoreRemote Computing Devices 150 may store a software application (e.g., theIntelligent Identity Scanning Module). In such embodiments, the systemmay be configured to provide the software application for installationon the One or More Remote Computing Devices 150. In particularembodiments, the software application may comprise one or more virtualmachines. In particular embodiments, the one or more virtual machinesmay be configured to perform one or more of the steps described abovewith respect to the Intelligent Identity Scanning Module 2600 (e.g.,perform the one or more steps locally on the One or More RemoteComputing Devices 150).

In various embodiments, the one or more virtual machines may have thefollowing specifications: (1) any suitable number of cores (e.g., 4, 6,8, etc.); (2) any suitable amount of memory (e.g., 4 GB, 8 GB, 16 GBetc.); (3) any suitable operating system (e.g., CentOS 7.2); and/or (4)any other suitable specification. In particular embodiments, the one ormore virtual machines may, for example, be used for one or more suitablepurposes related to the Intelligent Identity Scanning System 2700. Theseone or more suitable purposes may include, for example, running any ofthe one or more modules described herein, storing hashed and/ornon-hashed information (e.g., personal data, personally identifiabledata, catalog of individuals, etc.), storing and running one or moresearching and/or scanning engines (e.g., Elasticsearch), etc.

In various embodiments, the Intelligent Identity Scanning System 2700may be configured to distribute one or more processes that make up partof the Intelligent Identity Scanning Process (e.g., described above withrespect to the Intelligent Identity Scanning Module 1800). The one ormore software applications installed on the One or more Remote ComputingDevices 150 may, for example, be configured to provide access to the oneor more computer networks associated with the particular organization tothe Intelligent Identity Scanning Server 130. The system may then beconfigured to receive, from the One or more Remote Computing Devices 150at the Intelligent Identity Scanning Server 130, via the Firewall 195and One or More Networks 115, scanned data for analysis.

In particular embodiments, the Intelligent Identity Scanning System 2700is configured to reduce an impact on a performance of the One or MoreRemote Computing Devices 150, One or More Third Party Servers 160 andother components that make up one or more segments of the one or morecomputer networks associated with the particular organization. Forexample, in particular embodiments, the Intelligent Identity ScanningSystem 2700 may be configured to utilize one or more suitable bandwidththrottling techniques. In other embodiments, the Intelligent IdentityScanning System 2700 is configured to limit scanning (e.g., any of theone or more scanning steps described above with respect to theIntelligent Identity Scanning Module 2600) and other processing steps(e.g., one or more steps that utilize one or more processing resources)to non-peak times (e.g., during the evening, overnight, on weekendsand/or holidays, etc.). In other embodiments, the system is configuredto limit performance of such processing steps to backup applications anddata storage locations. The system may, for example, use one or moresampling techniques to decrease a number of records required to scanduring the personal data discovery process.

FIG. 28 depicts an exemplary asset access methodology that the systemmay utilize in order to access one or more network devices that maystore personal data (e.g., or other personally identifiableinformation). As may be understood from this figure, the system may beconfigured to access the one or more network devices using a locallydeployed software application (e.g., such as the software applicationdescribed immediately above). In various embodiments, the softwareapplication is configured to route identity scanning traffic through oneor more gateways, configure one or more ports to accept one or moreidentity scanning connections, etc.

As may be understood from this figure, the system may be configured toutilize one or more credential management techniques to access one ormore privileged network portions. The system may, in response toidentifying particular assets or personally identifiable information viaa scan, be configured to retrieve schema details such as, for example,an asset ID, Schema ID, connection string, credential reference URL,etc. In this way, the system may be configured to identify and store alocation of any discovered assets or personal data during a scan.

Data Subject Access Request Fulfillment Module

Turning to FIG. 29, in particular embodiments, a Data Subject AccessRequest Fulfillment Module 2900 is configured to receive a data subjectaccess request, process the request, and fulfill the request based atleast in part on one or more request parameters. In various embodiments,an organization, corporation, etc. may be required to provideinformation requested by an individual for whom the organization storespersonal data within a certain time period (e.g., 30 days). As aparticular example, an organization may be required to provide anindividual with a listing of, for example: (1) any personal data thatthe organization is processing for an individual, (2) an explanation ofthe categories of data being processed and the purpose of suchprocessing; and/or (3) categories of third parties to whom the data maybe disclosed.

Various privacy and security policies (e.g., such as the EuropeanUnion's General Data Protection Regulation, and other such policies) mayprovide data subjects (e.g., individuals, organizations, or otherentities) with certain rights related to the data subject's personaldata that is collected, stored, or otherwise processed by anorganization. These rights may include, for example: (1) a right toobtain confirmation of whether a particular organization is processingtheir personal data; (2) a right to obtain information about the purposeof the processing (e.g., one or more reasons for which the personal datawas collected); (3) a right to obtain information about one or morecategories of data being processed (e.g., what type of personal data isbeing collected, stored, etc.); (4) a right to obtain information aboutone or more categories of recipients with whom their personal data maybe shared (e.g., both internally within the organization or externally);(5) a right to obtain information about a time period for which theirpersonal data will be stored (e.g., or one or more criteria used todetermine that time period); (6) a right to obtain a copy of anypersonal data being processed (e.g., a right to receive a copy of theirpersonal data in a commonly used, machine-readable format); (7) a rightto request erasure (e.g., the right to be forgotten), rectification(e.g., correction or deletion of inaccurate data), or restriction ofprocessing of their personal data; and (8) any other suitable rightsrelated to the collection, storage, and/or processing of their personaldata (e.g., which may be provided by law, policy, industry ororganizational practice, etc.).

As may be understood in light of this disclosure, a particularorganization may undertake a plurality of different privacy campaigns,processing activities, etc. that involve the collection and storage ofpersonal data. In some embodiments, each of the plurality of differentprocessing activities may collect redundant data (e.g., may collect thesame personal data for a particular individual more than once), and maystore data and/or redundant data in one or more particular locations(e.g., on one or more different servers, in one or more differentdatabases, etc.). In this way, a particular organization may storepersonal data in a plurality of different locations which may includeone or more known and/or unknown locations. As such, complying withparticular privacy and security policies related to personal data (e.g.,such as responding to one or more requests by data subjects related totheir personal data) may be particularly difficult (e.g., in terms ofcost, time, etc.). In particular embodiments, a data subject accessrequest fulfillment system may utilize one or more data model generationand population techniques (e.g., such as any suitable techniquedescribed herein) to create a centralized data map with which the systemcan identify personal data stored, collected, or processed for aparticular data subject, a reason for the processing, and any otherinformation related to the processing.

Turning to FIG. 21, when executing the Data Subject Access RequestModule 2100, the system begins, at Step 2110, by receiving a datasubject access request. In various embodiments, the system receives therequest via a suitable web form. In certain embodiments, the requestcomprises a particular request to perform one or more actions with anypersonal data stored by a particular organization regarding therequestor. For example, in some embodiments, the request may include arequest to view one or more pieces of personal data stored by the systemregarding the requestor. In other embodiments, the request may include arequest to delete one or more pieces of personal data stored by thesystem regarding the requestor. In still other embodiments, the requestmay include a request to update one or more pieces of personal datastored by the system regarding the requestor. In still otherembodiments, the request may include a request based on any suitableright afforded to a data subject, such as those discussed above.

Continuing to Step 2120, the system is configured to process the requestby identifying and retrieving one or more pieces of personal dataassociated with the requestor that are being processed by the system.For example, in various embodiments, the system is configured toidentify any personal data stored in any database, server, or other datarepository associated with a particular organization. In variousembodiments, the system is configured to use one or more data models,such as those described above, to identify this personal data andsuitable related information (e.g., where the personal data is stored,who has access to the personal data, etc.). In various embodiments, thesystem is configured to use intelligent identity scanning (e.g., asdescribed above) to identify the requestor's personal data and relatedinformation that is to be used to fulfill the request.

In still other embodiments, the system is configured to use one or moremachine learning techniques to identify such personal data. For example,the system may identify particular stored personal data based on, forexample, a country in which a website that the data subject request wassubmitted is based, or any other suitable information.

In particular embodiments, the system is configured to scan and/orsearch one or more existing data models (e.g., one or more current datamodels) in response to receiving the request in order to identify theone or more pieces of personal data associated with the requestor. Thesystem may, for example, identify, based on one or more data inventories(e.g., one or more inventory attributes) a plurality of storagelocations that store personal data associated with the requestor. Inother embodiments, the system may be configured to generate a data modelor perform one or more scanning techniques in response to receiving therequest (e.g., in order to automatically fulfill the request).

Returning to Step 2130, the system is configured to take one or moreactions based at least in part on the request. In some embodiments, thesystem is configured to take one or more actions for which the requestwas submitted (e.g., display the personal data, delete the personaldata, correct the personal data, etc.). In particular embodiments, thesystem is configured to take the one or more actions substantiallyautomatically. In particular embodiments, in response a data subjectsubmitting a request to delete their personal data from anorganization's systems, the system may: (1) automatically determinewhere the data subject's personal data is stored; and (2) in response todetermining the location of the data (which may be on multiple computingsystems), automatically facilitate the deletion of the data subject'spersonal data from the various systems (e.g., by automatically assigninga plurality of tasks to delete data across multiple business systems toeffectively delete the data subject's personal data from the systems).In particular embodiments, the step of facilitating the deletion maycomprise, for example: (1) overwriting the data in memory; (2) markingthe data for overwrite; (2) marking the data as free (e.g., and deletinga directory entry associated with the data); and/or (3) any othersuitable technique for deleting the personal data. In particularembodiments, as part of this process, the system uses an appropriatedata model (see discussion above) to efficiently determine where all ofthe data subject's personal data is stored.

Data Subject Access Request User Experience

FIGS. 30-31 depict exemplary screen displays that a user may view whensubmitting a data subject access request. As shown in FIG. 30, a website30000 associated with a particular organization may include auser-selectable indicia 3005 for submitting a privacy-related request. Auser desiring to make such a request may select the indicia 3005 inorder to initiate the data subject access request process.

FIG. 31 depicts an exemplary data subject access request form in both anunfilled and filled out state. As shown in this figure, the system mayprompt a user to provide information such as, for example: (1) what typeof requestor the user is (e.g., employee, customer, etc.); (2) what therequest involves (e.g., requesting info, opting out, deleting data,updating data, etc.); (3) first name; (4) last name; (5) email address;(6) telephone number; (7) home address; and/or (8) one or more detailsassociated with the request.

As discussed in more detail above, a data subject may submit a subjectaccess request, for example, to request a listing of any personalinformation that a particular organization is currently storingregarding the data subject, to request that the personal data bedeleted, to opt out of allowing the organization to process the personaldata, etc.

Alternative Embodiment

In particular embodiments, a data modeling or other system describedherein may include one or more features in addition to those described.Various such alternative embodiments are described below.

Processing Activity and Data Asset Assessment Risk Flagging

In particular embodiments, the questionnaire template generation systemand assessment system described herein may incorporate one or more riskflagging systems. FIGS. 32-35 depict exemplary user interfaces thatinclude risk flagging of particular questions within a processingactivity assessment. As may be understood from these figures, a user mayselect a flag risk indicia to provide input related to a description ofrisks and mitigation of a risk posed by one or more inventory attributesassociated with the question. As shown in these figures, the system maybe configured to substantially automatically assign a risk to aparticular response to a question in a questionnaire. In variousembodiments, the assigned risk is determined based at least in part onthe template from which the assessment was generated.

In particular embodiments, the system may utilize the risk levelassigned to particular questionnaire responses as part of a riskanalysis of a particular processing activity or data asset. Varioustechniques for assessing the risk of various privacy campaigns aredescribed in U.S. patent application Ser. No. 15/256,419, filed Sep. 2,2016, entitled “Data processing systems and methods for operationalizingprivacy compliance and assessing the risk of various respective privacycampaigns,” which is hereby incorporated herein in its entirety.

Centralized Repository of Personally Identifiable Information (PII)Overview

A centralized data repository system, in various embodiments, isconfigured to provide a central data-storage repository (e.g., one ormore servers, databases, etc.) for the centralized storage of personallyidentifiable information (PII) and/or personal data for one or moreparticular data subjects. In particular embodiments, the centralizeddata repository may enable the system to populate one or more datamodels (e.g., using one or more suitable techniques described above)substantially on-the-fly (e.g., as the system collects, processes,stores, etc. personal data regarding a particular data subject). In thisway, in particular embodiments, the system is configured to maintain asubstantially up-to-date data model for a plurality of data subjects(e.g., each particular data subject for whom the system collects,processes, stores, etc. personal data). The system may then beconfigured to substantially automatically respond to one or more dataaccess requests by a data subject (e.g., individual, entity,organization, etc.), for example, using the substantially up-to-datedata model. In particular embodiments, the system may be configured torespond to the one or more data access requests using any suitabletechnique described herein.

As may be understood in light of this disclosure, a particularorganization may undertake a plurality of different privacy campaigns,processing activities, etc. that involve the collection and storage ofpersonal data. In some embodiments, each of the plurality of differentprocessing activities may collect redundant data (e.g., may collect thesame personal data for a particular individual more than once), and maystore data and/or redundant data in a plurality of different locations(e.g., on one or more different servers, in one or more differentdatabases, etc.). In this way, a particular organization may storepersonal data in a plurality of different locations which may includeone or more known and/or unknown locations. As such, complying withparticular privacy and security policies related to personal data (e.g.,such as responding to one or more requests by data subjects related totheir personal data) may be particularly difficult (e.g., in terms ofcost, time, etc.). Accordingly, utilizing and maintaining a centralizeddata repository for PII may enable the system to more quickly andaccurately respond to data subject access requests and other requestsrelated to collected, stored, and processed personal data. In particularembodiments, the centralized data repository may include one or morethird party data repositories (e.g., one or more third party datarepositories maintained on behalf of a particular entity that collects,stores, and/or processes personal data).

In various embodiments, a third party data repository system isconfigured to facilitate the receipt and centralized storage of personaldata for each of a plurality of respective data subjects. In particularembodiments, the system may be configured to: (1) receive personal dataassociated with a particular data subject (e.g., a copy of the data, alink to a location of where the data is stored, etc.); and (2) store thepersonal data in a suitable data format (e.g., a data model, a referencetable, etc.) for later retrieval. In other embodiments, the system maybe configured to receive an indication that personal data has beencollected regarding a particular data subject (e.g., collected by afirst party system, a software application utilized by a particularentity, etc.).

In particular embodiments, the third party data repository system isconfigured to: (1) receive an indication that a first party system(e.g., entity) has collected and/or processed a piece of personal datafor a data subject; (2) determine a location in which the first partysystem has stored the piece of personal data; (3) optionally digitallystore (e.g., in computer memory) a copy of the piece of personal dataand associate, in memory, the piece of personal data with the datasubject; and (4) optionally digitally store an indication of the storagelocation utilized by the first party system for the piece of personaldata. In particular embodiments, the system is configured to provide acentralized database, for each particular data subject (e.g., eachparticular data subject about whom a first party system collects or hascollected personally identifiable information), of any personal dataprocessed and/or collected by a particular entity.

In particular embodiments, a third party data repository system isconfigured to interface with a consent receipt management system (e.g.,such as the consent receipt management system described below). Inparticular embodiments, the system may, for example: (1) receive anindication of a consent receipt having an associated unique subjectidentifier and one or more receipt definitions (e.g., such as anysuitable definition described herein); (2) identify, based at least inpart on the one or more receipt definitions, one or more pieces ofrepository data associated with the consent receipt (e.g., one or moredata elements or pieces of personal data for which the consent receiptprovides consent to process; a storage location of the one or more dataelements for which the consent receipt provides consent to process;etc.); (3) digitally store the unique subject identifier in one or moresuitable data stores; and (4) digitally associate the unique subjectidentifier with the one or more pieces of repository data. In particularembodiments, the system is configured to store the personal dataprovided as part of the consent receipt in association with the uniquesubject identifier.

In particular embodiments, the system is configured to, for each storedunique subject identifier: (1) receive an indication that new personaldata has been provided by or collected from a data subject associatedwith the unique subject identifier (e.g., provided to an entity ororganization that collects and/or processes personal data); and (2) inresponse to receiving the indication, storing the new personal data(e.g., or storing an indication of a storage location of the newpersonal data by the entity) in association with the unique subjectidentifier. In this way, as an entity collects additional data for aparticular unique data subject (e.g., having a unique subjectidentifier, hash, etc.), the third party data repository system isconfigured to maintain a centralized database of data collected, stored,and or processed for each unique data subject (e.g., indexed by uniquesubject identifier). The system may then, in response to receiving adata subject access request from a particular data subject, fulfill therequest substantially automatically (e.g., by providing a copy of thepersonal data, deleting the personal data, indicating to the entity whatpersonal data needs to be deleted from their system and where it islocated, etc.). The system may, for example, automatically fulfill therequest by: (1) identifying the unique subject identifier associatedwith the unique data subject making the request; and (2) retrieving anyinformation associated with the unique data subject based on the uniquesubject identifier.

Exemplary Centralized Data Repository System Architecture

FIG. 36 is a block diagram of a centralized data repository system 3600according to a particular embodiment. In various embodiments, thecentralized data repository system 3600 is part of a privacy compliancesystem (also referred to as a privacy management system), or othersystem, which may, for example, be associated with a particularorganization and be configured to aid in compliance with one or morelegal or industry regulations related to the collection and storage ofpersonal data. In various other embodiments, the centralized datarepository system 3600 is a stand-alone system that is configured tointerface with one or more first party data management or other systemsfor the purpose of maintaining a centralized data repository of personaldata collected, stored, and/or processed by each of the one or morefirst party data systems.

As may be understood from FIG. 36, the centralized data repositorysystem 3600 includes one or more computer networks 115, One or MoreCentralized Data Repository Servers 3610, a Consent Receipt ManagementServer 3620, One or More First Party System Servers 3630, One or MoreDatabases 140 or other data structures, and one or more remote datasubject computing devices 3650 (e.g., a desktop computer, laptopcomputer, tablet computer, smartphone, etc.). In particular embodiments,the One or More Centralized Data Repository Servers 3610, ConsentReceipt Management Server 3620, One or More First Party System Servers3630, One or More Databases 140 or other data structures, and one ormore remote data subject computing devices 3650. Although in theembodiment shown in FIG. 36, the One or More Centralized Data RepositoryServers 3610, Consent Receipt Management Server 3620, One or More FirstParty System Servers 3630, One or More Databases 140 or other datastructures, and one or more remote data subject computing devices 3650are shown as separate servers, it should be understood that in otherembodiments, one or more of these servers and/or computing devices maycomprise a single server, a plurality of servers, one or morecloud-based servers, or any other suitable configuration.

In particular embodiments, the One or More Centralized Data RepositoryServers 3610 may be configured to interface with the One or More FirstParty System Servers 3630 to receive any of the indications or personaldata (e.g., for storage) described herein. The One or More CentralizedData Repository Servers 3610 and One or More First Party System Servers3630 may, for example, interface via a suitable application programminginterface, direct connection, etc. In a particular embodiment, the Oneor More Centralized Data Repository Servers 3610 comprise the ConsentReceipt Management Server 3620.

In a particular example, a data subject may provide one or more piecesof personal data via the One or More Remote Data Subject ComputingDevices 3650 to the One or More First Party System Servers 3630. Thedata subject may, for example, complete a webform on a website hosted onthe One or More First Party System Servers 3630. The system may then, inresponse to receiving the one or more pieces of personal data at the Oneor More First Party System Servers 3630, transmit an indication to theOne or More Centralized Data Repository Servers 3610 that the One orMore First Party System Servers 3630 have collected, stored, and/orprocessed the one or more pieces of personal data. In response toreceiving the indication, the One or More Centralized Data RepositoryServers 3610 may then store the one or more pieces of personal data(e.g., a copy of the data, an indication of the storage location of thepersonal data in the One or More First Party System Servers 3630, etc.)in a centralized data storage location (e.g., in One or More Databases140, on the One or More Centralized Data Repository Servers 3610, etc.).

Centralized Data Repository Module

Various functionality of the centralized data repository system 3600 maybe implemented via a Centralized Data Repository Module 3700. Thesystem, when executing certain steps of the Centralized Data RepositoryModule, may be configured to generate, a central repository of personaldata on behalf of an entity, and populate the central repository withpersonal data as the entity collects, stores and/or processes thepersonal data. In particular embodiments, the system is configured toindex the personal data within the central repository by data subject.

FIG. 37 depicts a Centralized Data Repository Module 3700 according to aparticular embodiment. The system, when executing the Centralized DataRepository Module 3700, begins, at Step 3710, by receiving a request togenerate a central repository of personal data on behalf of an entity.In particular embodiments, the system is a third-party system thatreceives a request from the entity to generate and maintain a centralrepository (e.g., third party repository) of personal data that theentity collects, stores, and or processes.

In particular embodiments, the system, in response to receiving therequest, is configured to generate the central repository by: (1)designating at least a portion of one or more data stores for thestorage of the personal data, information about the data subjects aboutwhom the personal data is collected, etc.; (2) initiating a connectionbetween the central repository and one or more data systems operated bythe entity (e.g., one or more first party systems); (3) etc.

Continuing to Step 3720, the system is configured to generate, for eachdata subject about whom the entity collects, receives, and/or processespersonal data, a unique identifier. The system may, for example: (1)receive an indication that a first party system has collected, stored,and/or processed a piece of personal data; (2) identify a data subjectassociated with the piece of personal data; (3) determine whether thecentral repository system is currently storing data associated with thedata subject; and (4) in response to determining that the centralrepository system is not currently storing data associated with the datasubject (e.g., because the data subject is a new data subject),generating the unique identifier. In various embodiments, the system isconfigured to assign a unique identifier for each data subject aboutwhom the first party system has previously collected, stored, and/orprocessed personal data.

In particular embodiments, the unique identifier may include any uniqueidentifier such as, for example: (1) any of the one or more pieces ofpersonal data collected, stored, and/or processed by the system (e.g.,name, first name, last name, full name, address, phone number, e-mailaddress, etc.); (2) a unique string or hash comprising any suitablenumber of numerals, letters, or combination thereof; and/or (3) anyother identifier that is sufficiently unique to distinguish between afirst and second data subject for the purpose of subsequent dataretrieval.

In particular embodiments, the system is configured to assign apermanent identifier to each particular data subject. In otherembodiments, the system is configured to assign one or more temporaryunique identifiers to the same data subject.

In particular embodiments, the unique identifier may be based at leastin part on the unique receipt key and/or unique subject identifierdiscussed below with respect to the consent receipt management system.As may be understood in light of this disclosure, when receiving consentform a data subject to process, collect, and at least store one or moreparticular types of personal data associated with the data subject, thesystem is configured to generate a unique ID to memorialize the consentand provide authorization for the system to collect the subject's data.In any embodiment described herein, the system may be configured toutilize any unique ID generated for the purposes of tracking datasubject consent as a unique identifier in the context of the centralrepository system described herein.

In particular embodiments, the system is configured to continue to Step3730, and store the unique identifier in computer memory. In particularembodiments, the system is configured to store the unique identifier inan encrypted manner. In various embodiments, the system is configured tostore the unique identifier in any suitable location (e.g., the one ormore databases 140 described above).

In particular embodiments, the system is configured to store the uniqueidentifier as a particular file structure such as, for example, aparticular folder structure in which the system is configured to storeone or more pieces of personal data (e.g., or pointers to one or morepieces of personal data) associated with the unique identifier (e.g.,the data subject associated with the unique identifier). In otherembodiments, the system is configured to store the unique identifier inany other suitable manner (e.g., in a suitable data table, etc.).

Returning to Step 3740, the system is configured to receive anindication that one or more computer systems have received, collected orprocessed one or more pieces of personal data associated with a datasubject. In particular embodiments, the one or more computer systemsinclude any suitable computer system associated with a particularentity. In other embodiments, the one or more computer systems compriseone or more software applications, data stores, databases, etc. thatcollect, process, and/or store data (e.g., personally identifiable data)on behalf of the entity (e.g., organization). In particular embodiments,the system is configured to receive the indication through integrationwith the one or more computer systems. In a particular example, thesystem may provide a software application for installation on a systemdevice that is configured to transmit the indication in response to thesystem receiving, collecting, and/or processing one or more pieces ofpersonal data.

In particular embodiments, the system may receive the indication inresponse to: (1) a first party system, data store, software application,etc. receiving, collecting, storing, and or processing a piece of datathat includes personally identifying information; (2) a user registeringfor an account with a particular entity (e.g., an online account,employee account, social media account, e-mail account, etc.); (3) acompany storing information about one or more data subjects (e.g.,employee information, customer information, potential customerinformation, etc.; and/or (4) any other suitable indication that a firstentity or any computer system or software on the first entity's behalfhas collected, stored, and/or processed a piece of data that includes ormay include personally identifiable information.

As a particular example, the system may receive the indication inresponse to a user submitting a webform via a website operated by thefirst entity. The webform may include, for example, one or more fieldsthat include the user's e-mail address, billing address, shippingaddress, and payment information for the purposes of collected paymentdata to complete a checkout process on an e-commerce website. In thisexample, because the information submitted via the webform containspersonal data (e.g., personally identifiable data) the system, inresponse to receiving an indication that the user has submitted the atleast partially completed webform, may be configured to receive theindication described above with respect to Step 3740.

In various embodiments, a first party privacy management system or othersystem (e.g., privacy management system, marketing system, employeerecords database management system, etc.) may be configured to transmitan indication to the central repository system in response tocollecting, receiving, or processing one or more pieces of personal datapersonal data.

In some embodiments, the indication may include, for example: (1) anindication of the type of personal data collected; (2) a purpose forwhich the personal data was collected; (3) a storage location of thepersonal data by the first party system; and/or (4) any other suitableinformation related to the one or more pieces of personal data or thehandling of the personal data by the first party system. In particularembodiments, the system is configured to receive the indication via anapplication programming interface, a software application stored locallyon a computing device within a network that makes up the first partysystem, or in any other suitable manner.

Continuing to Step 3750, the central repository system is configured tostore, in computer memory, an indication of the personal data inassociation with the respective unique identifier. In variousembodiments, the central repository system comprises a component of afirst party system for the centralized storage of personal datacollected by one or more various distributed computing systems (e.g.,and software applications) operated by a particular entity for thepurpose of collecting, storing, and/or processing personal data. Inother embodiments, the central repository system is a third-party datarepository system that is separate from the one or more first partysystems described above. In particular embodiments, for example, athird-party data repository system may be configured to maintain acentral repository of personal data for a plurality of differententities.

In particular embodiments, the central repository system is configuredto store a copy of the personal data (e.g., store a digital copy of thepersonal data in computer memory associated with the central repositorysystem). In still other embodiments, the central repository system isconfigured to store an indication of a storage location of the personaldata within the first party system. For example, the system may beconfigured to store an indication of a physical location of a particularstorage location (e.g., a physical location of a particular computerserver or other data store) and an indication of a location of thepersonal data in memory on that particular storage location (e.g., aparticular path or filename of the personal data, a particular locationin a spreadsheet, CSV file, or other suitable document, etc.).

In various embodiments, the system may be configured to confirm receiptof valid consent to collect, store, and/or process personal data fromthe data subject prior to storing the indication of the personal data inassociation with the respective unique identifier. In such embodiments,the system may be configured to integrate with (e.g., interface with) aconsent receipt management system (e.g., such as the consent receiptmanagement system described more fully below). In such embodiments, thesystem may be configured to: (1) receive the indication that the firstparty system has collected, stored, and/or processed a piece of personaldata; (2) identify, based at least in part on the piece of personaldata, a data subject associated with the piece of personal data; (3)determine, based at least in part on one or more consent receiptsreceived from the data subject(e.g., one or more valid receipt keysassociated with the data subject), and one or more pieces of informationassociated with the piece of personal data, whether the data subject hasprovided valid consent to collect, store, and/or process the piece ofpersonal data; (4) in response to determining that the data subject hasprovided valid consent, storing the piece of personal data in any mannerdescribed herein; and (5) in response to determining that the datasubject has not provided valid consent, deleting the piece of personaldata (e.g., not store the piece of personal data).

In particular embodiments, in response to determining that the datasubject has not provided valid consent, the system may be furtherconfigured to: (1) automatically determine where the data subject'spersonal data is stored (e.g., by the first party system); and (2) inresponse to determining the location of the data (which may be onmultiple computing systems), automatically facilitate the deletion ofthe data subject's personal data from the various systems (e.g., byautomatically assigning a plurality of tasks to delete data acrossmultiple business systems to effectively delete the data subject'spersonal data from the systems). In particular embodiments, the step offacilitating the deletion may comprise, for example: (1) overwriting thedata in memory; (2) marking the data for overwrite; (2) marking the dataas free (e.g., and deleting a directory entry associated with the data);and/or (3) any other suitable technique for deleting the personal data.

Next, at optional step 3760, the system is configured to take one ormore actions based at least in part on the data stored in associationwith the unique identifier. In particular embodiments, the one or moreactions may include, for example, responding to a data subject accessrequest initiated by a data subject (e.g., or other individual on thedata subject's behalf) associated with the unique identifier. In variousembodiments, the system is configured to identify the unique identifierassociated with the data subject making the data subject access requestbased on information submitted as part of the request.

Consent Receipt Management Systems

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireone or more of: (1) consent from a data subject from whom the personaldata is collected and/or processed; and/or (2) a lawful basis for thecollection and/or processing of the personal data. In variousembodiments, the entity may be required to, for example: (1) demonstratethat a data subject has freely given specific, informed, and unambiguousindication of the data subject's agreement to the processing of his orher personal data (e.g., in the form of a statement or clear affirmativeaction); (2) demonstrate that the entity received consent from a datasubject in a manner clearly distinguishable from other matters (e.g., inan intelligible and easily accessible form, using clear and plainlanguage, etc.); (3) enable a data subject to withdraw consent as easilyas the data subject can give consent; (4) separate a data subject'sconsent from performance under any contract unless such processing isnecessary for performance under the contract; etc.

In various embodiments, a consent receipt management system may beimplemented in the context of any suitable privacy management systemthat is configured to ensure compliance with one or more legal orindustry standards related to the collection and/or storage of privateinformation (e.g., such as personal data). Various privacy and securitypolicies (e.g., such as the European Union's General Data ProtectionRegulation, and other such policies) may provide data subjects (e.g.,individuals, organizations, or other entities) with certain rightsrelated to the data subject's personal data that is collected, stored,or otherwise processed by an organization. These rights may include, forexample: (1) a right to erasure of the data subject's personal data(e.g., in cases where no legal basis applies to the processing and/orcollection of the personal data; (2) a right to withdraw consent to theprocessing and/or collection of their personal data; (3) a right toreceive the personal data concerning the data subject, which he or shehas provided to an entity (e.g., organization), in a structured,commonly used and machine-readable format; and/or (4) any other rightwhich may be afforded to the data subject under any applicable legaland/or industry policy.

In particular embodiments, the consent receipt management system isconfigured to: (1) enable an entity to demonstrate that valid consenthas been obtained for each particular data subject for whom the entitycollects and/or processes personal data; and (2) enable one or more datasubjects to exercise one or more rights described herein.

The system may, for example, be configured to track data on behalf of anentity that collects and/or processes persona data related to: (1) whoconsented to the processing or collection of personal data (e.g., thedata subject themselves or a person legally entitled to consent on theirbehalf such as a parent, guardian, etc.); (2) when the consent was given(e.g., a date and time); (3) what information was provided to theconsenter at the time of consent (e.g., a privacy policy, what personaldata would be collected following the provision of the consent, for whatpurpose that personal data would be collected, etc.); (4) how consentwas received (e.g., one or more copies of a data capture form, webform,etc. via which consent was provided by the consenter); (5) when consentwas withdrawn (e.g., a date and time of consent withdrawal if theconsenter withdraws consent); and/or (6) any other suitable data relatedto receipt or withdrawal of consent.

In further embodiments, the system may be configured to provide datasubjects with a centralized interface that is configured to: (1) provideinformation regarding each of one or more valid consents that the datasubject has provided to one or more entities related to the collectionand/or processing of their personal data; (2) provide one or moreperiodic reminders regarding the data subject's right to withdrawpreviously given consent (e.g., every 6 months in the case ofcommunications data and metadata, etc.); (3) provide a withdrawalmechanism for the withdrawal of one or more previously provided validconsents (e.g., in a format that is substantially similar to a format inwhich the valid consent was given by the data subject); (4) refreshconsent when appropriate (e.g., the system may be configured to elicitupdated consent in cases where particular previously validly consentedto processing is used for a new purpose, a particular amount of time haselapsed since consent was given, etc.).

In particular embodiments, the system is configured to manage one ormore consent receipts between a data subject and an entity. In variousembodiments, a consent receipt may include a record (e.g., a data recordstored in memory and associated with the data subject) of consent, forexample, as a transactional agreement where the data subject is alreadyidentified or identifiable as part of the data processing that resultsfrom the provided consent. In any embodiment described herein, thesystem may be configured to generate a consent receipt in response to adata subject providing valid consent. In some embodiments, the system isconfigured to determine whether one or more conditions for valid consenthave been met prior to generating the consent receipt.

Exemplary Consent Receipt Data Flow

FIG. 38 depicts an exemplary data flow that a consent receipt managementsystem may utilize in the recordation and management of one or moreconsent receipts. In particular embodiments, a third party consentreceipt management system may be configured to manage one or moreconsent receipts for a particular entity. As may be understood from thisfigure, a data subject may access an interaction interface (e.g., viathe web) for interacting with a particular entity (e.g., one or moreentity systems). The interaction interface (e.g., user interface) mayinclude, for example, a suitable website, web form, user interface etc.The interaction interface may be provided by the entity. Using theinteraction interface, a data subject may initiate a transaction withthe entity that requires the data subject to provide valid consent(e.g., because the transaction includes the processing of personal databy the entity). The transaction may include, for example: (1) accessingthe entity's website; (2) signing up for a user account with the entity;(3) signing up for a mailing list with the entity; (4) a free trial signup; (5) product registration; and/or (6) any other suitable transactionthat may result in collection and/or processing personal data, by theentity, about the data subject.

As may be understood from this disclosure, any particular transactionmay record and/or require one or more valid consents from the datasubject. For example, the system may require a particular data subjectto provide consent for each particular type of personal data that willbe collected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, for example, by: (1) displaying, via the interaction interface,one or more pieces of information regarding the consent (e.g., whatpersonal data will be collected, how it will be used, etc.); and (2)prompt the data subject to provide the consent.

In response to the data subject (e.g., or the entity) initiating thetransaction, the system may be configured to: (1) generate a uniquereceipt key (e.g., unique receipt ID); (2) associate the unique receiptkey with the data subject (e.g., a unique subject identifier), theentity, and the transaction; and (3) electronically store (e.g., incomputer memory) the unique receipt key. The system may further store aunique user ID (e.g., unique subject identifier) associated with thedata subject (e.g., a hashed user ID, a unique user ID provided by thedata subject, unique ID based on a piece of personal data such as ane-mail address, etc.).

In a particular embodiment, the unique consent receipt key is generatedby a third party consent receipt management system. The system may thenbe configured to associate the unique consent receipt key with theinteraction interface, and further configured to associate the uniqueconsent receipt key with a unique transaction ID generated as a resultof a data subject transaction initiated via the interaction interface.

In particular embodiments, the unique consent receipt key may beassociated with one or more receipt definitions, which may include, forexample: (1) the unique transaction ID; (2) an identity of one or morecontrollers and/or representatives of the entity that is engaging in thetransaction with the data subject (e.g., and contact information for theone or more controllers); (3) one or more links to a privacy policyassociated with the transaction at the time that consent was given; (4)a listing of one or more data types for which consent to process wasprovided (e.g., email, MAC address, name, phone number, browsinghistory, etc.); (5) one or more methods used to collect data for whichconsent to process was provided (e.g., using one or more cookies,receiving the personal data from the data subject directly, etc.); (6) adescription of a service (e.g., a service provided as part of thetransaction such as a free trial, user account, etc.); (7) one or morepurposes of the processing (e.g., for marketing purposes, to facilitatecontact with the data subject, etc.); (8) a jurisdiction (e.g., theEuropean Union, United States, etc.); (9) a legal basis for thecollection of personal data (e.g., consent); (10) a type of consentprovided by the data subject (e.g. unambiguous, implicit, explicit,etc.); (11) one or more categories or identities of other entities towhom the personal data may be transferred; (12) one or more bases of atransfer to a third party entity (e.g., adequacy, binding corporaterules, etc.); (13) a retention period for the personal data (e.g., howlong the personal data will be stored); (14) a withdrawal mechanism(e.g., a link to a withdrawal mechanism); (15) a timestamp (e.g., dateand time); (16) a unique identifier for the receipt; and/or (17) anyother suitable information. FIG. 39 depicts an exemplary consentdefinition summary for a particular transaction (e.g., free trialsignup).

In response to receiving valid consent from the data subject, the systemis configured to transmit the unique transaction ID and the uniqueconsent receipt key back to the third party consent receipt managementsystem for processing and/or storage. In other embodiments, the systemis configured to transmit the transaction ID to a data store associatedwith one or more entity systems (e.g., for a particular entity on behalfof whom the third party consent receipt management system is obtainingand managing validly received consent). In further embodiments, thesystem is configured to transmit the unique transaction ID, the uniqueconsent receipt key, and any other suitable information related to thevalidly given consent to the centralized data repository systemdescribed above for use in determining whether to store particular dataand/or for assigning a unique identifier to a particular data subjectfor centralized data repository management purposes.

The system may be further configured to transmit a consent receipt tothe data subject which may include, for example: (1) the uniquetransaction ID; (2) the unique consent receipt key; and/or (3) any othersuitable data related to the validly provided consent. In someembodiments, the system is configured to transmit a consent receipt inany suitable format (e.g., JSON, HTML, e-mail, text, cookie, etc.). Inparticular embodiments, the receipt transmitted to the data subject mayinclude a link to a subject rights portal via which the data subjectmay, for example: (1) view one or more provided valid consents; (2)withdraw consent; (3) etc.

Exemplary Data Subject Consent Receipt User Experience

FIGS. 40 and 41 depict exemplary screen displays that a data subject mayencounter when providing consent to the processing of personal data. Asshown in FIG. 40, a data subject (e.g., John Doe) may provide particularpersonal data (e.g., first and last name, email, company, job title,phone number, etc.) when signing up for a free trial with a particularentity via a trial signup interface 4000. As may be understood in lightof this disclosure, the free trial may constitute a transaction betweenthe data subject (e.g., user) and a particular entity providing the freetrial. In various embodiments, the data subject (e.g., user) mayencounter the interface shown in FIG. 40 in response to accessing a website associated with the particular entity for the free trial (e.g., asign up page).

In particular embodiments, the interface 4000 is configured to enablethe user (e.g., data subject) to provide the information required tosign up for the free trial. As shown in FIG. 40, the interface furtherincludes a listing of particular things that the data subject isconsenting to (e.g., the processing of first name, last name, workemail, company, job title, and phone number) as well as one or morepurposes for the processing of such data (e.g., marketing information).The interface further includes a link to a Privacy Policy that governsthe use of the information.

In various embodiments, in response to the user (e.g., data subject)submitting the webform shown in FIG. 40, the system is configured togenerate a consent receipt that memorializes the user's provision of theconsent (e.g., by virtue of the user submitting the form). FIG. 41depicts an exemplary consent receipt 4100 in the form of a messagetransmitted to the data subject (e.g., via e-mail). As shown in thisfigure, the consent receipt includes, for example: (1) a receipt number(e.g., a hash, key, or other unique identifier); (2) what informationwas processed as a result of the user's consent (e.g., first and lastname, email, company, job title, phone number, etc.); (3) one or morepurposes of the processing (e.g., marketing information); (4)information regarding withdrawal of consent; (5) a link to withdrawconsent; and (6) a timestamp at which the system received the consent(e.g., a time at which the user submitted the form in FIG. 40). In otherembodiments, the consent receipt transmitted to the user may include anyother suitable information.

FIG. 42 depicts an exemplary log of consent receipts 4200 for aparticular transaction (e.g., the free trial signup described above). Asshown in this figure, the system is configured to maintain a database ofconsent receipts that includes, for example, a timestamp of eachreceipt, a unique key associated with each receipt, a customer IDassociated with each receipt (e.g., the customer's e-mail address), etc.In particular embodiments, the centralized data repository systemdescribed above may be configured to cross-reference the database ofconsent receipts (e.g., or maintain the database) in response toreceiving the indication that a first party system has received, stored,and/or processed personal data (e.g., via the free trial signupinterface) in order to confirm that the data subject has provided validconsent prior to storing the indication of the personal data.

Exemplary Transaction Creation User Experience

FIGS. 43-54 depict exemplary user interfaces via which a user (e.g., acontroller or other individual associated with a particular entity) maycreate a new transaction for which the system is configured to generatea new interaction interface (e.g., interface via which the system isconfigured to elicit and receive consent for the collection and/orprocessing of personal data from a data subject under the newtransaction.

As shown in FIG. 43, the system is configured to display a dashboard ofexisting transactions 4300 that are associated with a particular entity.In the example shown in this figure, the dashboard includes, forexample: (1) a name of each transaction; (2) a status of eachtransaction; (2) one or more data categories collected as part of eachtransaction; (3) a unique subject ID used as part of the transaction(e.g., email, device ID, etc.); (4) a creation date of each transaction;(5) a date of first consent receipt under each transaction; and (6) atotal number of receipts received for each transaction. The dashboardfurther includes a Create New Transaction button, which a user mayselect in order to create a new transaction.

As may be understood in light of this disclosure, in variousembodiments, the centralized data repository system described above maylimit storage of personal data on behalf of a particular entity tospecific personal data for which the particular entity has receivedconsent from particular data subjects. Based on the exemplary dashboardof existing transactions shown in FIG. 43, for example, the system maybe configured to not store any personal data collected, and/or processedother than in response to an indication that the data was collectedthrough the free trial signup or product registration transaction.

FIG. 44 depicts an interface 4400 for creating a new transaction, whicha user may access, for example, by selecting the Create New Transactionbutton shown in FIG. 43. As may be understood from this figure, whencreating a new transaction, the user may enter, via one or more textentry forms, a name of the transaction, a description of thetransaction, a group associated with the transaction, and/or any othersuitable information related to the new transaction.

Continuing to FIG. 45, the system may be configured to prompt the userto select whether the new transaction is based on an existing processingactivity. An existing processing activity may include, for example, anyother suitable transaction or any other activity that involves thecollection and/or processing of personal data. In response to the userselecting that the new transaction is not related to an existingprocessing activity (e.g., as shown in FIG. 45), the system may beconfigured to prompt the user, via one or more additional interfaces, toprovide information regarding the new transaction.

FIGS. 47-54 depict exemplary user interfaces via which the user mayprovide additional information regarding the new transaction. In variousembodiments, the system may be configured to prompt the user to providethe information via free-form text entry, via one or more drop downmenus, by selecting one or more predefined selections, or in anysuitable manner. In some embodiments, the system is configured to promptthe user to provide one or more standardized pieces of informationregarding the new transaction. In other embodiments, the system isconfigured to enable a particular entity (e.g., organization, company,etc.) to customize one or more questions or prompts that the systemdisplays to a user creating a new transaction.

As shown in FIG. 46, the system may, for example, prompt the user, viathe user interface, to: (1) describe a process or service that theconsent under the transaction relates to; (2) provide a public URL whereconsent is or will be collected; (3) provide information regarding howconsent is being collected (e.g., via a website, application, device,paper form, etc.); (4) provide information regarding one or more dataelements that will be processed based on the consent provided by thedata subject (e.g., what particular personal data will be collected);and (5) provide information regarding what data elements are processedby one or more background checks (e.g., credit check and/or criminalhistory).

Continuing to FIG. 47, the system may be configured to prompt the userto provide data related to, for example: (1) one or more elements thatwill be used to uniquely identify a data subject; (2) a purpose forseeking consent; (3) what type of consent is sought (e.g., unambiguous,explicit, not sure, etc.); (4) who is the data controller in charge ofthe processing of the personal data (e.g., the legal entityresponsible); (5) a contact address (e.g., for the data controller; (6)etc.

As shown in FIG. 48, the system may be further configured to prompt theuser to provide data regarding, for example: (1) who the contact personis for the transaction (e.g., a job title, name, etc. of the contactperson); (2) a contact email (e.g., an email address that a data subjectcan contact to get more information about the transaction, consent,etc.); (3) a contact telephone number (e.g., a telephone number that adata subject can contact to get more information about the transaction,consent, etc.); (4) an applicable jurisdiction for the processing (e.g.,European Union, United States, Other, etc.), which may include one ormore jurisdictions; (5) a URL of a privacy policy associated with thetransaction; (6) etc.

Next, as shown in FIG. 49, the system may be further configured toprompt the user to provide data regarding: (1) whether the personal datawill be shared with one or more third parties; (2) a name of the one ormore third parties; (3) whether the processing of the personal data willinvolve a transfer of the personal data outside of the originaljurisdiction; (4) a listing of one or more destination countries,regions, or other jurisdictions that will be involved in anyinternational transfer; (5) a process for a data subject to withdrawconsent; (6) a URL for the withdrawal mechanism; (7) etc. FIG. 50depicts a user interface that includes additional data prompts for theuser to respond to regarding the new transaction. As shown in FIG. 50,the system may be further configured to prompt the user to provide dataregarding, for example: (1) what the retention period is for thepersonal data (e.g., how long the personal data will be stored inidentifiable form, a period before anonymization of the personal data,etc.); and/or (2) a life span of the consent (e.g., a period of timeduring which the consent is assumed to be valid).

FIG. 51 shows an exemplary user interface for selecting a processingactivity in response to the user indicating that the new transaction isbased on an existing processing activity. The user may, for example, usea drop down menu to select a suitable existing processing activity. Inparticular embodiments, the system is configured to populate the dropdown menu with one or more processing activities from a data modelassociated with the processing activity. The system may then beconfigured to substantially automatically populate one or more responsesto the questions described above based at least in part on the datamodel (e.g., automatically include particular data elements collected aspart of the processing activity, etc.).

In particular embodiments, the system is further configured to enable acontroller (e.g., or other user on behalf of the entity) to search forone or more consent receipts received for a particular data subject(e.g., via a unique subject identifier). FIG. 52 depicts a search for aunique subject identifier that includes an e-mail address. As shown inthis figure, the unique subject identifier (e.g., john.doe@gmail.com)has one associated consent receipt having a receipt number, a receiptdate and time, and a withdrawal date. FIG. 53 depicts an additionalexemplary search results page indicating one or more results for consentreceipts associated with the unique subject identifier ofjohn.doe@gmail.com. As shown in this figure, the system may beconfigured to display a process name (e.g., transaction name), receiptnumber, consent date, status, withdrawal date, and other suitableinformation for one or more consent receipts associated with thesearched for unique subject identifier.

As may be understood in light of this disclosure, in response to a usercreating a new transaction, the system may be configured to generate aweb form, web page, piece of computer code, etc. for the collection ofconsent by a data subject as part of the new transaction. FIG. 54depicts an exemplary dashboard of consent receipt managementimplementation code which the system may automatically generate for theimplementation of a consent receipt management system for a particulartransaction. As shown in this figure, the system displays particularcomputer code (e.g., in one or more different programming language) thatthe system has generated. A user may place the generated code on awebpage or other location that the user desires to collect consent.

Exemplary Consent Receipt Management System Architecture

FIG. 55 is a block diagram of a Consent Receipt Management System 5500according to a particular embodiment. In some embodiments, the ConsentReceipt Management System 5500 is configured to interface with at leasta portion of each respective organization's Privacy Compliance System inorder generate, capture, and maintain a record of one or more consentsto process, collect, and or store personal data from one or more datasubjects.

As may be understood from FIG. 55, the Consent Receipt Management System5500 includes one or more computer networks 115, a Consent ReceiptManagement Server 5510, a Consent Receipt Capture Server 5520 (e.g.,which may be configured to run one or more virtual browsers 5525 asdescribed herein), One or More Consent Web Form Hosting Servers 5530,one or more databases 140, and one or more remote computing devices 5550(e.g., a desktop computer, laptop computer, tablet computer, etc.). Inparticular embodiments, the one or more computer networks 115 facilitatecommunication between the Consent Receipt Management Server 5510, aConsent Receipt Capture Server 5520, One or More Consent Web FormHosting Servers 5530, one or more databases 140, and one or more remotecomputing devices 5550.

The one or more computer networks 115 may include any of a variety oftypes of wired or wireless computer networks such as the Internet, aprivate intranet, a public switch telephone network (PSTN), or any othertype of network. The communication link between Consent Receipt CaptureServer 5520 and Database 140 may be, for example, implemented via aLocal Area Network (LAN) or via the Internet.

Exemplary Consent Receipt Management System Platform

Various embodiments of a Consent Receipt Management System 5500 4500 maybe implemented in the context of any suitable system (e.g., a privacycompliance system). For example, the Consent Receipt Management System5500 may be implemented to facilitate receipt and maintenance of one ormore valid consents provided by one or more data subjects for theprocessing and/or at least temporary storage of personal data associatedwith the data subjects. In particular embodiments, the system mayimplement one or more modules in order to at least partially ensurecompliance with one or more regulations (e.g., legal requirements)related to the collection and/or storage of personal data. Variousaspects of the system's functionality may be executed by certain systemmodules, including a Consent Receipt Management Module 5600, a ConsentExpiration and Re-Triggering Module 5700, and a Consent Validity ScoringModule 5900. These modules are discussed in greater detail below.

Although the system may be configured to execute the functions describedin the modules as a series of steps, it should be understood in light ofthis disclosure that various embodiments of the Consent ReceiptManagement Module 5600, Consent Expiration and Re-Triggering Module5700, and Consent Validity Scoring Module 5900 described herein mayperform the steps described below in an order other than in which theyare presented. In still other embodiments, the Consent ReceiptManagement Module 5600, Consent Expiration and Re-Triggering Module5700, and Consent Validity Scoring Module 5900 may omit certain stepsdescribed below. In various other embodiments, the Consent ReceiptManagement Module 5600, Consent Expiration and Re-Triggering Module5700, and Consent Validity Scoring Module 5900 may perform steps inaddition to those described (e.g., such as one or more steps describedwith respect to one or more other modules, etc.).

Consent Receipt Generation

In various embodiments, a consent receipt management system isconfigured to generate a consent receipt for a data subject that linksto (e.g., in computer memory) metadata identifying a particular purposeof the collection and/or processing of personal data that the datasubject consented to, a capture point of the consent (e.g., a copy ofthe web form or other mechanism through which the data subject providedconsent, and other data associated with one or more ways in which thedata subject granted consent.

The system may, for example, be configured to track data on behalf of anentity that collects and/or processes persona data related to: (1) whoconsented to the processing or collection of personal data (e.g., thedata subject themselves or a person legally entitled to consent on theirbehalf such as a parent, guardian, etc.); (2) when the consent was given(e.g., a date and time); (3) what information was provided to theconsenter at the time of consent (e.g., a privacy policy, what personaldata would be collected following the provision of the consent, for whatpurpose that personal data would be collected, etc.); (4) how consentwas received (e.g., one or more copies of a data capture form, web form,etc. via which consent was provided by the consenter); (5) when consentwas withdrawn (e.g., a date and time of consent withdrawal if theconsenter withdraws consent); and/or (6) any other suitable data relatedto receipt or withdrawal of consent.

Using an interaction interface, a data subject may initiate atransaction with the entity that requires the data subject to providevalid consent (e.g., because the transaction includes the processing ofpersonal data by the entity). The transaction may include, for example:(1) accessing the entity's website (e.g., which may utilize one or morecookies and/or other tracking technologies to monitor the data subject'sactivity while accessing the website or other websites); (2) signing upfor a user account with the entity; (3) signing up for a mailing listwith the entity; (4) a free trial sign up; (5) product registration;and/or (6) any other suitable transaction that may result in collectionand/or processing of personal data, by the entity, about the datasubject.

As may be understood from this disclosure, any particular transactionmay record and/or require one or more valid consents from the datasubject. For example, the system may require a particular data subjectto provide consent for each particular type of personal data that willbe collected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, for example, by: (1) displaying, via the interaction interface,one or more pieces of information regarding the consent (e.g., whatpersonal data will be collected, how it will be used, etc.); and (2)prompt the data subject to provide the consent.

In response to the data subject (e.g., or the entity) initiating thetransaction, the system may be configured to: (1) generate a uniquereceipt key (e.g., unique receipt ID); (2) associate the unique receiptkey with the data subject (e.g., via a unique subject identifier), theentity, and the transaction; and (3) electronically store (e.g., incomputer memory) the unique receipt key. The system may further store aunique user ID (e.g., unique subject identifier) associated with thedata subject (e.g., a hashed user ID, a unique user ID provided by thedata subject, unique ID based on a piece of personal data such as ane-mail address, etc.). In other embodiments, the system may beconfigured to store computer code associated with the capture of theconsent by the system. The system may, for example, store computer codeassociated with a web form or other consent capture mechanism. In otherembodiments, the system is configured to capture one or more images ofone or more webpages via which a data subject provides (e.g., provided)consent (e.g., substantially at the time at which the data subjectprovided consent). This may, for example, enable an entity or otherorganization to demonstrate one or more conditions under which consentwas received for a particular data subject in order to comply with oneor more regulations related to the securing of consent.

In a particular embodiment, the system is configured to: (1) use avirtual web browser to access a URL via which a data subject providedconsent for a particular processing activity or other transaction; (2)capture one or more images of one or more web sites at the URL, the oneor more images containing one or more web forms or other portions of theone or more web pages via which the data subject provided one or moreinputs that demonstrated the data subject's consent; and store the oneor more images in association with metadata associated with one or moreconsent receipts related to the received consent. In some embodiments,the system may be configured to: (1) scan, via the virtual web browser,a particular website and/or URL; (2) identify a web form at theparticular website and/or URL; and (3) capture one or more images (e.g.,screenshots) of the web form (e.g., in an unfilled-out state). In someembodiments, the system is configured to use a virtual web browser thatcorresponds to a web browser via which the user completed the web form.For example, the system may be configured to identify a particular webbrowser utilized by the data subject, and initiate the virtual browsingsession using the identified web browser.

FIG. 55 depicts an exemplary Consent Receipt Management Module 5500 thatincludes steps that the system may execute in order to generate aconsent receipt. As may be understood from FIG. 55, the system may beconfigured to: (1) provide a user interface for initiating a transactionbetween an entity and a data subject (e.g., such as a web form via whichthe data subject may authorize or consent to the processing, collection,or storage of personal data associated with the transaction); (2)receive a request to initiate a transaction between the entity and thedata subject (e.g., from a computing device associated with the datasubject via a web form located at a particular URL, on a particularwebpage, etc.); (3) in response to receiving the request, generating, bya third party consent receipt management system, a unique consentreceipt key; (4) in response to receiving the request, initiating avirtual browsing session on a second computing device (e.g., a secondcomputing device associated with the third party consent receiptmanagement system); (5) using the virtual browser to access theparticular URL or particular webpage that hosts the web form; (6)capturing, via the virtual browser, one or more images of the web form,the URL, and/or the particular webpage; (7) store a unique subjectidentifier associated with the data subject, the unique consent receiptkey, a unique transaction identifier associated with the transaction,and the one or more images in computer memory; and (8) electronicallyassociating the unique subject identifier, the unique consent receiptkey, the unique transaction identifier, and the one or more images.

FIG. 40 depicts an exemplary screen display that a data subject mayencounter when providing consent to the processing of personal data. Asshown in FIG. 40, a data subject (e.g., John Doe) may provide particularpersonal data (e.g., first and last name, email, company, job title,phone number, etc.) when signing up for a free trial with a particularentity. As may be understood in light of this disclosure, the free trialmay constitute a transaction between the data subject (e.g., user) and aparticular entity providing the free trial. In various embodiments, thedata subject (e.g., user) may encounter the interface shown in FIG. 40in response to accessing a web site associated with the particularentity for the free trial (e.g., a sign up page).

In particular embodiments, the interface is configured to enable theuser (e.g., data subject) to provide the information required to sign upfor the free trial. As shown in FIG. 40, the interface further includesa listing of particular things that the data subject is consenting to(e.g., the processing of first name, last name, work email, company, jobtitle, and phone number) as well as one or more purposes for theprocessing of such data (e.g., marketing information). The interfacefurther includes a link to a Privacy Policy that governs the use of theinformation.

In various embodiments, in response to the user (e.g., data subject)submitting the webform shown in FIG. 40, the system is configured togenerate a consent receipt that memorializes the user's provision of theconsent (e.g., by virtue of the user submitting the form). FIG. 40depicts an uncompleted version of the web form from FIG. 40 that thesystem may capture via a virtual browsing session described herein andstore in association with the consent receipt. FIG. 41 depicts anexemplary consent receipt in the form of a message transmitted to thedata subject (e.g., via e-mail). As shown in this figure, the consentreceipt includes, for example: (1) a receipt number (e.g., a hash, key,or other unique identifier); (2) what information was processed as aresult of the user's consent (e.g., first and last name, email, company,job title, phone number, etc.); (3) one or more purposes of theprocessing (e.g., marketing information); (4) information regardingwithdrawal of consent; (5) a link to withdraw consent; and (6) atimestamp at which the system received the consent (e.g., a time atwhich the user submitted the form in FIG. 2). In other embodiments, theconsent receipt transmitted to the user may include any other suitableinformation (e.g., such as a link to an unfilled out version of the webform via which the user provided consent, etc.)

In particular embodiments, the system is configured to generate a codeassociated with a particular web form. The system may then associate thecode with a particular website, mobile application, or other locationthat hosts the web form.

In various other embodiments, the system is configured to capture one ormore images (e.g., and/or one or more copies) of one or more privacypolicies and/or privacy notices associated with the transaction orprocessing activity. This may include, for example, one or more privacypolicies and/or privacy notices that dictate one or more terms underwhich the data subject provided consent (e.g., consent to have personaldata associated with the data subject processed, collected, and/orstored). The system may be further configured to store and associate thecaptured one or more privacy policies and/or privacy notices with one ormore of the unique subject identifier, the unique consent receipt key,the unique transaction identifier, etc.

In various embodiments, the system is configured to generate a web formfor use by an entity to capture consent from one or more data subjects.In other embodiments, the system is configured to integrate with anexisting web form. The system may, for example, be configured to recordeach particular selection and/or text entry by the data subject via theweb form and capture (e.g., via the virtual browsing session describedabove) one or more images (e.g., screenshots) which may demonstrate whatthe web form looked like at the time the consent was provided (e.g., inan unfilled out state).

As may be understood in light of this disclosure, in response to a usercreating a new transaction on behalf of an entity, the system may beconfigured to generate a web form, web page, piece of computer code,etc. for the collection of consent by a data subject as part of the newtransaction. FIG. 54 depicts an exemplary dashboard of consent receiptmanagement implementation code which the system may automaticallygenerate for the implementation of a consent receipt management systemfor a particular transaction. As shown in this figure, the systemdisplays particular computer code (e.g., in one or more differentprogramming language) that the system has generated. A user may placethe generated code on a webpage, within a mobile application, or otherlocation that the user desires to collect consent.

In some embodiments, the system is configured to capture and store theunderlying code for a particular web form (e.g., HTML or other suitablecomputer code), which may, for example, be used to demonstrate how theconsent from the data subject was captured at the time of the capture.In some embodiments, the system may be configured to capture theunderlying code via the virtual browsing session described above.

In particular embodiments, the system is configured to enable an entityto track one or more consent provisions or revocations received via oneor more venues other than via a computing device. For example, a datasubject may provide or revoke consent via: (1) a phone call; (2) viapaper (e.g., paper mailing); and/or (3) any other suitable avenue. Thesystem may, for example, provide an interface via which a customersupport representation can log a phone call from a data subject (e.g., arecording of the phone call) and generate a receipt indicating that thecall occurred, what was requested on the call, whether the request wasfulfilled, and a recording of the call. Similarly, the system may beconfigured to provide an interface to scan or capture one or more imagesof one or more consents provided or revoked via mail (e.g., snail mail).

Consent Receipts—Automatic Expiration and Triggering of ConsentRecapture

In particular embodiments, the consent receipt management system isconfigured to: (1) automatically cause a prior, validly received consentto expire (e.g., in response to a triggering event); and (2) in responseto causing the previously received consent to expire, automaticallytrigger a recapture of consent. In particular embodiments, the systemmay, for example, be configured to cause a prior, validly receivedconsent to expire in response to one or more triggering events such as:(1) a passage of a particular amount of time since the system receivedthe valid consent (e.g., a particular number of days, weeks, months,etc.); (2) one or more changes to a purpose of the data collection forwhich consent was received (e.g., or one or more other changes to one ormore conditions under which the consent was received; (3) one or morechanges to a privacy policy associated with the consent; (3) one or morechanges to one or more rules (e.g., laws, regulations, etc.) that governthe collection or demonstration of validly received consent; and/or (4)any other suitable triggering event or combination of events. Inparticular embodiments, such as any embodiment described herein, thesystem may be configured to link a particular consent received from adata subject to a particular version of a privacy policy, to aparticular version of a web form through which the data subject providedthe consent, etc. The system may then be configured to detect one ormore changes to the underlying privacy policy, consent receiptmethodology, etc., and, in response, automatically expire one or moreconsents provided by one or more data subjects under a previous versionof the privacy policy or consent capture form.

In various embodiments, the system may be configured to substantiallyautomatically expire a particular data subject's prior provided consentin response to a change in location of the data subject. The system may,for example, determine that a data subject is currently located in ajurisdiction, country, or other geographic location other than thelocation in which the data subject provided consent for the collectionand/or processing of their personal data. The system may be configuredto determine that the data subject is in a new location based at leastin part on, for example, a geolocation (e.g., GPS location) of a mobilecomputing device associated with the data subject, an IP address of oneor more computing devices associated with the data subject, etc.). Asmay be understood in light of this disclosure, one or more differentcountries, jurisdictions, etc. may impose different rules, regulations,etc. related to the collection, storage, and processing of personaldata. As such, in response to a user moving to a new location (e.g., orin response to a user temporarily being present in a new location), thesystem may be configured to trigger a recapture of consent based on oneor more differences between one or more rules or regulations in the newlocation and the original location from which the data subject providedconsent. In some embodiments, the system may substantially automaticallycompare the one or more rules and/or regulations of the new and originallocations to determine whether a recapture of consent is necessary.

In particular embodiments, in response to the automatic expiration ofconsent, the system may be configured to automatically trigger arecapture of consent (e.g., based on the triggering event). The systemmay, for example, prompt the data subject to re-provide consent using,for example: (1) an updated version of the relevant privacy policy; (2)an updated web form that provides one or more new purposes for thecollection of particular personal data; (3) one or more web forms orother consent capture methodologies that comply with one or more changesto one or more legal, industry, or other regulations; and/or (4) etc.

FIG. 57 depicts an exemplary Consent Expiration and Re-Triggering Module5700 according to a particular embodiment. In various embodiments, whenexecuting the Consent Expiration and Re-Triggering Module 5700, thesystem is configured to, beginning at Step 5710, by determining that atriggering event has occurred. In various embodiments, the triggeringevent may include nay suitable triggering event such as, for example:(1) passage of a particular amount of time since a valid consent wasreceived; (2) determination that a data subject for which the system haspreviously received consent is now located in a new jurisdiction,country, geographic location, etc.; (3) a change to one or more uses ofdata for which the data subject provided consent for the collectionand/or processing; (4) a change to one or more privacy policies; and/or(5) any other suitable triggering event related to one or more consentsreceived by the system.

Continuing to Step 5720, the system is configured to cause an expirationof at least one validly received consent in response to determining thatthe triggering event has occurred. In response to causing the expirationof the at least one consent, the system may be configured to ceaseprocessing, collecting, and/or storing personal data associated with theprior provided consent (e.g., that has now expired). The system maythen, at Step 5730, in response to causing the expiration of the atleast one validly received consent, automatically trigger a recapture ofthe at least one expired consent.

Consent Preference Modification Capture Systems

In particular embodiments, the consent receipt management system isconfigured to provide a centralized repository of consent receiptpreferences for a plurality of data subjects. In various embodiments,the system is configured to provide an interface to the plurality ofdata subjects for modifying consent preferences and capture consentpreference changes. The system may provide the ability to track theconsent status of pending and confirmed consents. In other embodiments,the system may provide a centralized repository of consent receipts thata third-party system may reference when taking one or more actionsrelated to a processing activity. For example, a particular entity mayprovide a newsletter that one or more data subjects have consented toreceiving. Each of the one or more data subjects may have differentpreferences related to how frequently they would like to receive thenewsletter, etc. In particular embodiments, the consent receiptmanagement system may receive a request from a third-party system totransmit the newsletter to the plurality of data subjects. The systemmay then cross-reference an updated consent database to determine whichof the data subjects have a current consent to receive the newsletter,and whether transmitting the newsletter would conflict with any of thosedata subjects' particular frequency preferences. The system may then beconfigured to transmit the newsletter to the appropriate identified datasubjects.

In particular embodiments, the system may be configured to identifyparticular consents requiring a double opt-in (e.g., an initial consentfollowed by a confirmatory consent in respond to generation of aninitial consent receipt in order for consent to be valid). In particularembodiments, the system may track consents with a “half opt-in” consentstatus, and take one or more steps to complete the consent (e.g., one ormore steps described below with respect to consent conversionanalytics).

The system may also, in particular embodiments, proactively modifysubscriptions or other preferences for users in similar demographicsbased on machine learning of other users in that demographic opting tomake such modifications. For example, the system may be configured tomodify a user's preferences related to a subscription frequency for anewsletter or make other modifications in response to determining thatone or more similarly situated data subjects (e.g., subjects of similarage, gender, occupation, etc.) have made such modifications. In variousembodiments, the system may be configured to increase a number of datasubjects that maintain consent to particular processing activities whileensuring that the entity undertaking the processing activities complieswith one or more regulations that apply to the processing activities.

Consent Conversion Analytics

In particular embodiments, a consent receipt management system isconfigured to track and analyze one or more attributes of a userinterface via which data subjects are requested to provide consent(e.g., consent to process, collect, and/or store personal data) in orderto determine which of the one or more attributes are more likely toresult in a successful receipt of consent from a data subject. Forexample, the system may be configured to analyze one or more instancesin which one or more data subjects provided or did not provide consentin order to identify particular attributes and/or factors that mayincrease a likelihood of a data subject providing consent. The one ormore attributes may include, for example: (1) a time of day at whichparticular data subjects provided/did not provide consent; (2) a lengthof an e-mail requesting consent in response to which particular datasubjects provided/did not provide consent; (3) a number of e-mailsrequesting consent in a particular time period sent to particular datasubjects in response to at least one of which particular data subjectsprovided/did not provide consent; (4) how purpose-specific a particularemail requesting consent was; (5) whether an e-mail requesting consentprovided one or more opt-down options (e.g., one or more options toconsent to receive a newsletter less frequently); (5) whether the e-mailrequesting consent included an offer; (6) how compelling the offer was;(7) etc. The system may then aggregate these analyzed attributes andwhether specific attributes increased or decreased a likelihood that aparticular data subject may provide consent and use the aggregatedanalysis to automatically design a user interface, e-mail message, etc.that is configured to maximize consent receipt conversion based on theanalytics.

In particular embodiments, the system may further be configured togenerate a customized interface or message requesting consent for aparticular data subject based at least in part on an analysis ofsimilarly situated data subjects that provided consent based onparticular attributes of an e-mail message or interface via which theconsent was provided. For example, the system may identify one or moresimilarly situated data subjects based at least in part on: (1) age; (2)gender; (3) occupation; (4) income level; (5) interests, etc. Inparticular embodiments, a male between the ages of 18-25 may, forexample, respond to a request for consent with a first set of attributesmore favorably than a woman between the ages of 45 and 50 (e.g., who mayrespond more favorably to a second set of attributes).

The system may be configured to analyze a complete consent journey(e.g., from initial consent, to consent confirmation in cases where adouble opt-in is required to validly receive consent). In particularembodiments, the system is configured to design interfaces particularlyto capture the second step of a double opt-in consent or to recaptureconsent in response to a change in conditions under which consent wasinitially provided.

In particular embodiments, the system may be configured to use theanalytics described herein to determine a particular layout,interaction, time of day, number of e-mails, etc. cause the highestconversion rate across a plurality of data subjects (e.g., across aplurality of similarly situated data subjects of a similar demographic).

FIG. 58 depicts an exemplary consent conversion analysis interface. Asmay be understood from this figure, the system may be configured totrack, for example: (1) total unique visitors to a particular website(e.g., to which the system may attempt to obtain consent for particulardata processing); (2) overall opt-in percentage of consent; (3) opt-inpercent by actions; (4) opt-out percentage by actions, etc.

Consent Validity Scoring Systems

In particular embodiments, a consent receipt management system mayinclude one or more consent validity scoring systems. In variousembodiments, a consent validity scoring system may be configured todetect a likelihood that a user is correctly consenting via a web form.The system may be configured to determine such a likelihood based atleast in part on one or more data subject behaviors while the datasubject is completing the web form in order to provide consent. Invarious embodiments, the system is configured to monitor the datasubject behavior based on, for example: (1) mouse speed; (2) mousehovering; (3) mouse position; (4) keyboard inputs; (5) an amount of timespent completing the web form; and/or (5) any other suitable behavior orattribute. The system may be further configured to calculate a consentvalidity score for each generated consent receipt based at least in parton an analysis of the data subject's behavior (e.g., inputs, lack ofinputs, time spent completing the consent form, etc.).

In particular embodiments, the system is configured to monitor the datasubject's (e.g., the user's) system inputs while the data subject iscompeting a particular web form. In particular embodiments activelymonitoring the user's system inputs may include, for example,monitoring, recording, tracking, and/or otherwise taking account of theuser's system inputs. These system inputs may include, for example: (1)one or more mouse inputs; (2) one or more keyboard (e.g., text) inputs;(3) one or more touch inputs; and/or (4) any other suitable inputs(e.g., such as one or more vocal inputs, etc.). In other embodiments,the system is configured to monitor one or more biometric indicatorsassociated with the user such as, for example, heart rate, pupildilation, perspiration rate, etc. In other embodiments, the system isconfigured to track a user's scrolling speed, scrolling distance, or anyother suitable factor.

In particular embodiments, the system is configured to monitor a user'sinputs, for example, by substantially automatically tracking a locationof the user's mouse pointer with respect to one or more selectableobjects on a display screen of a computing device. In particularembodiments, the one or more selectable objects are one or moreselectable objects (e.g., indicia) that make up part of the web form. Instill other embodiments, the system is configured to monitor a user'sselection of any of the one or more selectable objects, which mayinclude, for example, an initial selection of one or more selectableobjects that the user subsequently changes to selection of a differentone of the one or more selectable objects.

In any embodiment described herein, the system may be configured tomonitor one or more keyboard inputs (e.g., text inputs) by the user thatmay include, for example, one or more keyboard inputs that the userenters or one or more keyboard inputs that the user enters but deleteswithout submitting. The user may, for example, initially begin typing afirst response, but delete the first response and enter a secondresponse that the user ultimately submits. In various embodiments of thesystem described herein, the system is configured to monitor theun-submitted first response in addition to the submitted secondresponse.

In still other embodiments, the system is configured to monitor a user'slack of input. For example, a user may mouse over a particular inputindicia (e.g., a selection from a drop-down menu, a radio button orother selectable indicia) without selecting the selection or indicia. Inparticular embodiments, the system is configured to monitor such inputs.As may be understood in light of this disclosure, a user that mousesover a particular selection and lingers over the selection withoutactually selecting it may, for example, be demonstrating an uncertaintyregarding the consent the user is providing.

In other embodiments, the system is configured to monitor any othersuitable input by the user. In various embodiments, this may include,for example: (1) monitoring one or more changes to an input by a user;(2) monitoring one or more inputs that the user later removes ordeletes; (3) monitoring an amount of time that the user spends providinga particular input; and/or (4) monitoring or otherwise tracking anyother suitable information.

In various embodiments, the system is further configured to determinewhether a user has accessed and/or actually scrolled through a privacypolicy associated with a particular transaction. The system may furtherdetermine whether a user has opened an e-mail that includes a summary ofthe consent provided by the user after submission of the web form. Thesystem may then be configured to use any suitable information related tothe completion of the web form or other user activity to calculate aconsent validity score. In various embodiments, the consent validityscore may indicate, for example: (1) an ease at which the user was ableto complete a particular consent form; (2) an indication that aparticular consent may or may not have been freely given; (3) etc. Inparticular embodiments, the system may be configured to trigger arecapture of consent in response to calculating a consent validity scorefor a particular consent that is below a particular amount. In otherembodiment, the system may be configured to confirm a particular user'sconsent depending on a calculated validity score for the consent.

FIG. 59 depicts an exemplary Consent Validity Scoring Module 5900. Asmay be understood from FIG. 59, in various embodiments, when executingthe Consent Validity Scoring Module 5900, the system begins at Step5910, by identifying and analyzing one or more data subject behaviorswhile the data subject is providing consent for particular dataprocessing. In various embodiments, the one or more data subjectbehaviors may include any suitable data subject behavior describedherein. Continuing to Step 5920, the system is configured to determine avalidity score for the provided consent based at least in part on theanalysis at Step 5910. The system may then be configured to optionallytrigger a recapture of consent based on the determined validity score.The system may, for example, be configured to capture a recapture ofconsent in response to determining that that the validity score is belowa predetermined level.

In various embodiments, the consent validity core may be based on a typeof consent for a particular transaction (e.g., processing, storage,collection, etc. of data). For example, the consent validity score maybe based on whether consent was received explicitly (e.g., in responseto explicit selection of an indicia or other button related to therequested consent) or implicitly (e.g., in response to the userscrolling past a particular point on a website, the user continuing toaccess a website after display of an indication that continued use wouldbe taken as consent, etc.).

Conclusion

Although embodiments above are described in reference to various privacycompliance monitoring systems, it should be understood that variousaspects of the system described above may be applicable to otherprivacy-related systems, or to other types of systems, in general.

While this specification contains many specific embodiment details,these should not be construed as limitations on the scope of anyinvention or of what may be claimed, but rather as descriptions offeatures that may be specific to particular embodiments of particularinventions. Certain features that are described in this specification inthe context of separate embodiments may also be implemented incombination in a single embodiment. Conversely, various features thatare described in the context of a single embodiment may also beimplemented in multiple embodiments separately or in any suitablesub-combination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination may in some cases be excisedfrom the combination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems maygenerally be integrated together in a single software product orpackaged into multiple software products.

Many modifications and other embodiments of the invention will come tomind to one skilled in the art to which this invention pertains havingthe benefit of the teachings presented in the foregoing descriptions andthe associated drawings. Therefore, it is to be understood that theinvention is not to be limited to the specific embodiments disclosed andthat modifications and other embodiments are intended to be includedwithin the scope of the appended claims. Although specific terms areemployed herein, they are used in a generic and descriptive sense onlyand not for the purposes of limitation.

What is claimed is:
 1. A data processing consent optimization systemcomprising: one or more processors; computer memory; and acomputer-readable medium storing computer-executable instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform operations comprising: providing, to a pluralityof data subjects, a user interface for initiating a transaction betweenan entity and each respective data subject of the plurality of datasubjects; at least partially in response to providing the user interfaceto the plurality of data subjects, receiving one or more requests toinitiate the transaction from at least a first portion of the pluralityof data subjects; analyzing, by one or more processors, the one or morerequests to identify one or more first factors associated with at leasta first portion of the one or more requests, wherein the one or morefirst factors comprise at least one factor selected from the groupconsisting of: a time of day at which each of the plurality of datasubjects viewed the user interface; how purpose-specific the userinterface the transaction is; and whether the user interface forinitiating the transaction included an offer; analyzing, by one or moreprocessors, the one or more first factors of the user interface todetermine at least one factor of the one or more first factors thatincrease a likelihood that a particular data subject will submit arequest to initiate the transaction; storing an indication of the atleast one factor in computer memory; generating a new user interface forinitiating the transaction based at least in part on the at least onefactor, wherein generating the new user interface comprises determininga layout of the new user interface based at least in part on the atleast one factor; and providing the new user interface for initiatingthe transaction to at least one data subject.
 2. The data processingconsent optimization system of claim 1, wherein: the user interfacecomprises an electronic message; and the one or more first factorscomprise a length of the electronic message.
 3. The data processingconsent optimization system of claim 1, wherein: the user interfacecomprises an electronic message; and the one or more first factorscomprise an opt-down option within the electronic message.
 4. The dataprocessing consent optimization system of claim 1, wherein generatingthe new user interface comprises generating the new user interface tonot include one or more of the one or more attributes.
 5. The dataprocessing consent optimization system of claim 1, wherein thecomputer-readable medium further stores computer-executable instructionsthat, when executed by the one or more processors, cause the one or moreprocessors to perform operations comprising providing the new userinterface to the plurality of data subjects that do not include the atleast the first portion of the plurality of data subjects.
 6. Acomputer-implemented data processing method for optimizing consent for atransaction, the method comprising: providing, by one or moreprocessors, to a first plurality of data subjects, a first userinterface having a first set of user interface attributes to eachrespective data subject of the first plurality of data subjects, thefirst user interface being a first user interface for initiating atransaction between an entity and each respective data subject of thefirst plurality of data subjects; providing, by one or more processors,to a second plurality of data subjects, a second user interface having asecond set of user interface attributes to each respective data subjectof the second plurality of data subjects, the second user interfacebeing a second user interface for initiating a transaction between theentity and each respective data subject of the second plurality of datasubjects; receiving, by one or more processors, one or more firstrequests to initiate the transaction from at least a first portion ofthe first plurality of data subjects; receiving, by one or moreprocessors, one or more second requests to initiate the transaction fromat least a second portion of the second plurality of data subjects;analyzing, by one or more processors, the one or more first requests andthe one or more second requests to identify one or more commonattributes among the first set of user interface attributes and thesecond set of user interface attributes; analyzing, by one or moreprocessors, the one or more common attributes of the first userinterface and the second user interface to determine, based on the oneor more first requests and the one or more second requests, at least oneattribute that increases a likelihood that a particular data subjectwill submit a request to initiate the transaction; storing an indicationof the one or more common attributes in computer memory; and generatinga custom consent interface for initiating the transaction based at leastin part on the and the at least one attribute, wherein generating thecustom consent interface comprises determining a layout of the custominterface based at least in part on the at least one attribute.
 7. Thecomputer-implemented data processing method of claim 6, the methodfurther comprising: analyzing the first portion of the first pluralityof data subjects to categorize the first portion of the first pluralityof data subjects based on one or more first data subject attributes;analyzing the second portion of the second plurality of data subjects tocategorize the second portion of the second plurality of data subjectsbased on one or more second data subject attributes; and comparing theone or more first data subject attributes and the one or more seconddata subject attributes to identify one or more shared data subjectattributes; generating the custom consent interface for initiating thetransaction based at least further in part on the one or more shareddata subject attributes.
 8. The computer-implemented data processingmethod of claim 7, wherein the one or more shared data subjectattributes are selected from the group consisting of: age; gender; andoccupation.
 9. The computer-implemented data processing method of claim8, the method further comprising providing the custom consent interfacefor initiating the transaction to a particular data subject based atleast in part on the one or more shared data subject attributes.
 10. Thecomputer-implemented data processing method of claim 6, wherein thetransaction comprises processing, by the entity, one or more pieces ofpersonal data associated with the first plurality of data subjects andthe second plurality of data subjects.
 11. The computer-implemented dataprocessing method of claim 6, wherein the first user interface is thesecond user interface,
 12. The computer-implemented data processingmethod of claim 6, the method further comprising: tracking a number ofthe first plurality of data subjects that viewed the first userinterface; determining, based at least in part on the first portion ofthe first plurality of data subjects, an overall opt-in percentage forthe first user interface; and displaying the number of the firstplurality of data subjects that viewed the first user interface and theoverall opt-in percentage to a first user via a consent conversioninterface.
 13. The computer-implemented data processing method of claim12, wherein: the transaction comprises one or more transaction options;and the method further comprises tracking a selection of each of the oneor more transaction options and displaying the selection of each of theone or more transaction options as part of the consent conversioninterface.
 14. A consent receipt analysis, processing, and custominterface generation system comprising; one or more processors; computermemory; and a non-transitory computer-readable medium storingcomputer-executable instructions that, when executed by the one or moreprocessors, cause the one or more processors to perform operationscomprising: providing, by one or more processors, to a first pluralityof data subjects, a first user interface having a first set of userinterface factors to each respective data subject of the first pluralityof data subjects, the first user interface being a first user interfacefor initiating a first transaction between an entity and each respectivedata subject of the first plurality of data subjects; providing, by oneor more processors, to a second plurality of data subjects, a seconduser interface having a second set of user interface factors to eachrespective data subject of the second plurality of data subjects, thesecond user interface being a second user interface for initiating asecond transaction between the entity and each respective data subjectof the second plurality of data subjects; receiving, by one or moreprocessors, one or more first requests to initiate the first transactionfrom at least a first portion of the first plurality of data subjects;receiving, by one or more processors, one or more second requests toinitiate the second transaction from at least a second portion of thesecond plurality of data subjects; analyzing, by one or more processors,the one or more first requests and the one or more second requests toidentify one or more common factors among the first set of userinterface factors and the second set of user interface factors;analyzing, by one or more processors, the one or more common factors ofthe first user interface and the second user interface to determine,based on the one or more first requests and the one or more secondrequests, at least one factor that increases a likelihood that aparticular data subject will submit a request to initiate the firsttransaction or the second transaction; storing an indication of the atleast one factor in computer memory; and generating a custom consentinterface for initiating a third transaction based at least in part onthe at least one factor, wherein generating the custom consent interfacecomprises determining a layout of the custom consent interface based atleast in part on the at least one factor.
 15. The consent receiptanalysis, processing, and custom interface generation system of claim14, wherein the one or more common factors are selected from the groupconsisting of: a type of the first transaction; a type of the secondtransaction; a number of first opt-down options available via the firstuser interface; a number of second opt-down options available via thefirst user interface; a time of day at which the first user interfacewas provided to the first plurality of data subjects; a time of day atwhich the second user interface was provided to the second plurality ofdata subjects; an age of the first plurality of data subjects; an age ofthe second plurality of data subjects; a gender of the first pluralityof data subjects; and a gender of the second plurality of data subjects.16. The consent receipt analysis, processing, and custom interfacegeneration system of claim 15, wherein the one or more common factorscomprise a type of the first transaction and a type of the secondtransaction.
 17. The consent receipt analysis, processing, and custominterface generation system of claim 14, wherein the non-transitorycomputer-readable medium further stores computer-executable instructionsthat, when executed by the one or more processors, cause the one or moreprocessors to perform operations comprising providing the custom consentinterface to a second portion of the first plurality of data subjectsthat does not include the first portion of the first plurality of datasubjects.
 18. The consent receipt analysis, processing, and custominterface generation system of claim 14, wherein the non-transitorycomputer-readable medium further stores computer-executable instructionsthat, when executed by the one or more processors, cause the one or moreprocessors to perform operations comprising: analyzing the first portionof the first plurality of data subjects to categorize the first portionof the first plurality of data subjects based on one or more first datasubject attributes; analyzing the second portion of the second pluralityof data subjects to categorize the second portion of the secondplurality of data subjects based on one or more second data subjectattributes; comparing the one or more first data subject attributes andthe one or more second data subject attributes to identify one or moreshared data subject attributes; and generating the custom consentinterface for initiating the third transaction based at least further inpart on the one or more shared data subject attributes.
 19. The consentreceipt analysis, processing, and custom interface generation system ofclaim 14, wherein the non-transitory computer-readable medium furtherstores computer-executable instructions that, when executed by the oneor more processors, cause the one or more processors to performoperations comprising providing the custom consent interface forinitiating the third transaction to a particular data subject based atleast in part on the one or more shared data subject attributes.
 20. Theconsent receipt analysis, processing, and custom interface generationsystem of claim 19, wherein the one or more shared data subjectattributes are selected from the group consisting of: age; gender; andoccupation.